Top issues
Detected presence of software components with dependencies that are hosted outside the official project repository.
hunting
Problem
Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Each of these components can have dozens, or even hundreds, of its own dependencies. When building applications, software developers download and install components from public repositories. For components to work properly, all of their dependencies also need to be installed. Some package repositories, like Node Package Manager (NPM), allow components to declare dependencies that are hosted remotely. Such dependencies are automatically downloaded from a specified location during software component installation. Since remotely hosted dependencies are not immutable, that enables a threat actor to change the dependency contents even after a component was published and vetted by security solutions. It is uncommon to find open source components that use remotely hosted dependencies residing outside the official project source code repository.Prevalence in npm community
5 packages
found in
Top 100
21 packages
found in
Top 1k
383 packages
found in
Top 10k
36.49k packages
in community
Next steps
Review software component remote dependency locations.
If the software component resolves dependencies from unusual locations, investigate the build and release environment for software supply chain compromise.
Consider vendoring the software component with all of its dependencies.
Avoid using this software package until it is vetted as safe.
Problem
Software components contain executable code that performs actions implemented during its development. These actions are called behaviors. In the analysis report, behaviors are presented as human-readable descriptions that best match the underlying code intent. While most behaviors are benign, some are commonly abused by malicious software with the intent to cause harm. When a software package shares behavior traits with malicious software, it may become flagged by security solutions. Any detection from security solutions can cause friction for the end-users during software deployment. While the behavior is likely intended by the developer, there is a small chance this detection is true positive, and an early indication of a software supply chain attack.Prevalence in npm community
9 packages
found in
Top 100
29 packages
found in
Top 1k
255 packages
found in
Top 10k
95.32k packages
in community
Next steps
Investigate reported detections.
If the software intent does not relate to the reported behavior, investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed, or until the issue is risk accepted.
Consider rewriting the flagged code without using the marked behaviors.
Problem
Software developers use programming and design knowledge to build reusable software components. Software components are the basic building blocks for modern applications. Software consumed by an enterprise consists of hundreds, and sometimes even thousands of open source components. Each of these components can have dozens, or even hundreds, of its own dependencies. When building applications, software developers download and install components from public repositories. For components to work properly, all of their dependencies also need to be installed. Some package repositories, like Node Package Manager (NPM), allow components to declare dependencies that are hosted remotely. Such dependencies are automatically downloaded from a specified location during software component installation. Since remotely hosted dependencies are not immutable, that enables a threat actor to change the dependency contents even after a component was published and vetted by security solutions. It is uncommon to find open source components that use remotely hosted source dependencies.Prevalence in npm community
8 packages
found in
Top 100
43 packages
found in
Top 1k
554 packages
found in
Top 10k
64.5k packages
in community
Next steps
Review software component remote dependency locations.
If the software component resolves dependencies from unusual locations, investigate the build and release environment for software supply chain compromise.
Consider vendoring the software component with all of its dependencies.
Avoid using this software package until it is vetted as safe.
Top behaviors
Might contain potentially obfuscated code or data.
anomaly
Prevalence in npm community
Behavior often found in this community (Common)
22 packages
found in
Top 100
136 packages
found in
Top 1k
1267 packages
found in
Top 10k
411.22k packages
in community
Opens URLs during installation or upon launch.
network
Prevalence in npm community
Behavior often found in this community (Common)
7 packages
found in
Top 100
40 packages
found in
Top 1k
645 packages
found in
Top 10k
86.51k packages
in community
Executes files during installation or upon launch.
execution
Prevalence in npm community
Behavior often found in this community (Common)
95 packages
found in
Top 100
726 packages
found in
Top 1k
7488 packages
found in
Top 10k
4.56M packages
in community
Contains Visa credit card numbers.
steal
Prevalence in npm community
Behavior often found in this community (Common)
0 packages
found in
Top 100
4 packages
found in
Top 1k
77 packages
found in
Top 10k
22.75k packages
in community
The software package contains remotely hosted source dependencies.
anomaly
Prevalence in npm community
Behavior commonly used by malicious software (Important)
Behavior often found in this community (Common)
8 packages
found in
Top 100
43 packages
found in
Top 1k
554 packages
found in
Top 10k
64.5k packages
in community
Top vulnerabilities
No vulnerabilities found.