Top issues
Detected presence of software components with malicious dependencies.
Causes risk: malicious dependencies found
threats
Problem
Proprietary ReversingLabs malware detection algorithms have determined that the software package has one or more malicious dependencies. Some software dependencies may be optional, and could be installed or downloaded only if a certain pre-defined condition is met. When software dependencies are confirmed to be found within the software package, additional issues might also be reported. The detection was made by either a static byte signature, software component identity, or a complete file hash. This malware detection method is considered highly accurate, and can typically attribute malware to previously discovered software supply chain attacks.Prevalence in npm community
0 packages
found in
Top 100
4 packages
found in
Top 1k
37 packages
found in
Top 10k
7092 packages
in community
Next steps
Inspect behaviors exhibited by the detected software components.
If the software behaviors differ from expected, investigate the build and release environment for software supply chain compromise.
Revise the use of components that raise these alarms. If you can't deprecate those components, make sure they are well-documented.
Avoid using this software package until it is vetted as safe.
Detected presence of severe vulnerabilities with active exploitation.
Causes risk: actively exploited vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known severe vulnerabilities. Available threat intelligence telemetry has confirmed that the reported high or critical severity vulnerabilities are actively being exploited by malicious actors.Prevalence in npm community
34 packages
found in
Top 100
152 packages
found in
Top 1k
1955 packages
found in
Top 10k
777714 packages
in community
Next steps
We strongly advise updating the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Detected presence of high severity vulnerabilities.
Causes risk: high severity vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Based on the CVSS scoring, these vulnerabilities have been marked as high severity.Prevalence in npm community
32 packages
found in
Top 100
168 packages
found in
Top 1k
2061 packages
found in
Top 10k
805890 packages
in community
Next steps
Perform impact analysis for the reported CVEs.
Update the component to the latest version.
If the update can't resolve the issue, create a plan to isolate or replace the affected component.
Top behaviors
Executes files during installation or upon launch.
execution
Prevalence in npm community
No behavior prevalence information at this timeContains URLs with unusual hostname lengths.
network
Prevalence in npm community
Behavior often found in this community (Common)
7 packages
found in
Top 100
52 packages
found in
Top 1k
886 packages
found in
Top 10k
616361 packages
in community
Queries the value of an environment variable.
search
Prevalence in npm community
Behavior often found in this community (Common)
32 packages
found in
Top 100
147 packages
found in
Top 1k
2296 packages
found in
Top 10k
636391 packages
in community
Enumerates files in a given directory.
search
Prevalence in npm community
Behavior often found in this community (Common)
17 packages
found in
Top 100
77 packages
found in
Top 1k
884 packages
found in
Top 10k
222519 packages
in community
Emits an event, effectively calling each of the registered listeners for that event.
behavior
Prevalence in npm community
Behavior often found in this community (Common)
11 packages
found in
Top 100
67 packages
found in
Top 1k
693 packages
found in
Top 10k
114630 packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(3 Active Vulnerabilities)
None
2 (2 Fixable)
CVE-2020-28469h
CVE-2024-4068h
None
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated