MAL-2026-10464: Malicious code in node-procmetrics-data (npm)
The node-procmetrics-data package version 1.0.1 contains malicious code that, upon installation or execution, archives the installer's root filesystem (excluding certain system directories) and exfiltrates the data by publishing it in chunks as new versions of the package to the public npm registry. It uses a hardcoded, obfuscated npm authentication token to authenticate and write to the installer's npm configuration, abusing the npm registry as a covert data exfiltration channel. This behavior extends the attacker's footprint by programmatically publishing new package versions from the compromised machine.
AI Analysis
Technical Summary
[email protected] includes a malicious script (archive-sender.js) that collects the installer's root filesystem data (excluding /proc, /sys, /dev, /tmp, /run), compresses it into a tar archive, splits it into 200MB chunks, and exfiltrates these chunks by publishing them as new versions of the package to the public npm registry. The package contains a hardcoded npm authentication token obfuscated via XOR with 0x5A, which is written into the npm config to enable publishing. This technique abuses the npm registry as a covert channel for data exfiltration and allows the attacker to expand their presence by publishing additional malicious package versions from the victim's environment.
Potential Impact
Sensitive data from the installer's root filesystem can be exfiltrated without detection through the npm registry. The attacker gains the ability to publish new package versions from the compromised environment, potentially spreading malicious code further. This compromises confidentiality and integrity of the affected system and the npm ecosystem.
Mitigation Recommendations
No official patch or remediation is currently documented. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for current remediation guidance. Users should immediately remove and avoid using node-procmetrics-data version 1.0.1. Audit npm packages for unauthorized publishing activity and revoke any exposed npm authentication tokens. Consider rotating npm credentials and monitoring for suspicious package publication.
MAL-2026-10464: Malicious code in node-procmetrics-data (npm)
Description
The node-procmetrics-data package version 1.0.1 contains malicious code that, upon installation or execution, archives the installer's root filesystem (excluding certain system directories) and exfiltrates the data by publishing it in chunks as new versions of the package to the public npm registry. It uses a hardcoded, obfuscated npm authentication token to authenticate and write to the installer's npm configuration, abusing the npm registry as a covert data exfiltration channel. This behavior extends the attacker's footprint by programmatically publishing new package versions from the compromised machine.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
[email protected] includes a malicious script (archive-sender.js) that collects the installer's root filesystem data (excluding /proc, /sys, /dev, /tmp, /run), compresses it into a tar archive, splits it into 200MB chunks, and exfiltrates these chunks by publishing them as new versions of the package to the public npm registry. The package contains a hardcoded npm authentication token obfuscated via XOR with 0x5A, which is written into the npm config to enable publishing. This technique abuses the npm registry as a covert channel for data exfiltration and allows the attacker to expand their presence by publishing additional malicious package versions from the victim's environment.
Potential Impact
Sensitive data from the installer's root filesystem can be exfiltrated without detection through the npm registry. The attacker gains the ability to publish new package versions from the compromised environment, potentially spreading malicious code further. This compromises confidentiality and integrity of the affected system and the npm ecosystem.
Mitigation Recommendations
No official patch or remediation is currently documented. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for current remediation guidance. Users should immediately remove and avoid using node-procmetrics-data version 1.0.1. Audit npm packages for unauthorized publishing activity and revoke any exposed npm authentication tokens. Consider rotating npm credentials and monitoring for suspicious package publication.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10464
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ffb868715ace432facc3
Added to database: 07/14/2026, 09:22:00 UTC
Last enriched: 07/14/2026, 10:00:03 UTC
Last updated: 07/14/2026, 17:23:25 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.