Top issues
Detected presence of known software supply chain attack artifacts.
Causes risk: supply chain attack artifacts
threats
Problem
Proprietary ReversingLabs malware detection algorithms have determined that the software package contains one or more malicious components. 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. It is common to have multiple supply chain attack artifacts that relate to a single malware incident.Prevalence in npm community
0 packages
found in
Top 100
1 packages
found in
Top 1k
18 packages
found in
Top 10k
14717 packages
in community
Next steps
If the software intent does not relate to malicious behavior, investigate the build and release environment for software supply chain compromise.
Avoid using this software package.
Detected presence of malicious files through analyst-vetted file reputation.
Causes risk: analyst-vetted malware found
threats
Problem
Threat researchers have manually inspected the software package and determined that it contains one or more malicious files. The detection was made by a hash-based file reputation lookup. This malware detection method is considered highly accurate, and can typically identify the malware family by name.Prevalence in npm community
0 packages
found in
Top 100
1 packages
found in
Top 1k
17 packages
found in
Top 10k
15236 packages
in community
Next steps
Investigate the build and release environment for software supply chain compromise.
Avoid using this software package.
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 malware-exploited vulnerabilities.
Causes risk: malware exploited vulnerabilities
vulnerabilities
Problem
Software composition analysis has identified a component with one or more known vulnerabilities. Available threat intelligence telemetry has confirmed that the reported vulnerabilities are actively being exploited by malicious actors. Malware code that propagates through these vulnerabilities has been created. This increases the chance of automated malware attacks affecting the software component users.Prevalence in npm community
2 packages
found in
Top 100
2 packages
found in
Top 1k
220 packages
found in
Top 10k
279466 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 files with behaviors that match the infostealer malware profile.
Causes risk: malware-like behaviors found
hunting
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 exclusively used by malicious software with the intent to cause harm. When a software package matches behavior traits of malicious software, it becomes flagged by security solutions. It is highly likely that the software package was tampered with by a malicious actor or a rogue insider. Detected threat type matches the behaviors typically exhibited by the infostealer malware profile. Infostealers are commonly used to steal sensitive user data such as stored login details, financial information, and other personally identifiable information.Prevalence in npm community
0 packages
found in
Top 100
0 packages
found in
Top 1k
2 packages
found in
Top 10k
10214 packages
in community
Next steps
Investigate reported detections.
Investigate your build and release environment for software supply chain compromise.
You should delay the software release until the investigation is completed.
In the case this behavior is intended, rewrite the flagged code without using the malware-like behaviors.
Top behaviors
Deletes files in Windows system directories.
file
Prevalence in npm community
Behavior often found in this community (Common)
0 packages
found in
Top 100
1 packages
found in
Top 1k
31 packages
found in
Top 10k
8142 packages
in community
Contains common certificate strings.
settings
Prevalence in npm community
Behavior often found in this community (Common)
0 packages
found in
Top 100
1 packages
found in
Top 1k
29 packages
found in
Top 10k
8404 packages
in community
Encrypts or encodes files and other data using the Windows Cryptography API.
file
Prevalence in npm community
Behavior uncommon for this community (Uncommon)
0 packages
found in
Top 100
0 packages
found in
Top 1k
0 packages
found in
Top 10k
634 packages
in community
Executes files during installation or upon launch.
execution
Prevalence in npm community
No behavior prevalence information at this timeChecks operating system version.
search
Prevalence in npm community
Behavior often found in this community (Common)
0 packages
found in
Top 100
1 packages
found in
Top 1k
54 packages
found in
Top 10k
13379 packages
in community
Top vulnerabilities
Vulnerability Exploitation Lifecycle
(5 Active Vulnerabilities)
None
5 (5 Fixable)
CVE-2025-54313h
CVE-2025-9086h
CVE-2025-4947m
1 (1 Fixable)
CVE-2025-54313h
None
Exploits Unknown
Exploits Exist
Exploited by Malware
Patching Mandated