Malicious code in -pem-misa (npm)
The npm package -pem-misa contains malicious code designed to automatically generate and republish derivative packages with randomized names to the npm registry. The attack is part of a broader tea.xyz token reward campaign that flooded npm with similar malicious packages.
- Disclosed
- Last updated
- Blast radius
- Registry-wide pollution; affects any developer who installed -pem-misa or its auto-generated derivative packages
- Ecosystems
- Attack vectors
- Affected entities
- -pem-misanpm package containing malicious autopublish scripts
The npm package -pem-misa was identified as containing malicious code by Amazon Inspector and credited to OpenSSF's malicious-packages repository. The package includes autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) designed to automatically generate and publish derivative packages with randomized names, primarily using Indonesian-themed naming conventions.\n\nThe malicious payload modifies package.json to remove private flags and changes version numbers, enabling continuous republication of variants to pollute the npm registry. This activity is part of a larger coordinated campaign associated with the tea.xyz token reward system, which flooded npm with numerous similar malicious packages intended to inflate developer reputation scores for token rewards.\n\nThe attack vector involves compromised or intentionally malicious package uploads that execute autopublish logic upon installation, creating a cascading effect of registry pollution and potential supply chain contamination for downstream consumers.
Indicators of compromise
- Packages
- -pem-misa
Remediation
- Remove -pem-misa and any derivative packages with randomized or suspicious names from your dependencies immediately
- Audit npm package.json and lock files for any unexpected or unfamiliar packages, particularly those with randomized or unusual naming patterns
- Review npm account activity and authentication logs for unauthorized package publications
- Consider using npm audit and security scanning tools to detect similar malicious packages in your environment
- Report any installed instances of this package to npm security team
Sources
- GitHub Advisory GHSA-fffx-vm7c-rv7c · GitHub Advisory Database
Cite this entry
"Malicious code in -pem-misa (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 25, 2026; last updated July 25, 2026. https://supplychainattack.org/incident/malicious-code-in-pem-misa-npm-3znbom
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Injective SDK on npm infected with cryptocurrency wallet stealer
Hackers compromised the Injective Labs SDK GitHub repository and published a malicious npm package that stole cryptocurrency wallet private keys and mnemonic seed phrases from users who installed it.
npmCompromised packageMalicious commit - activecritical
Miasma npm Supply Chain Attack: Self-Spreading Worm via Phantom Gyp
A self-replicating worm named Miasma is spreading across the npm registry by injecting malicious code into binding.gyp files, which execute during npm install without requiring package.json script modifications. The attack has already compromised dozens of packages across multiple maintainer accounts and evades conventional security detection.
MiasmanpmCompromised packageMalicious commit - activehigh
Supply Chain Campaign Targets SAP npm Packages with Credential-Stealing Malware
A supply chain campaign dubbed "Mini Shai Hulud" targeted SAP npm packages with malicious versions containing credential-stealing malware. The campaign follows patterns similar to previous Shai-Hulud attacks.
Mini Shai HuludShai-HuludnpmCompromised packageMalicious commit - resolvedhigh
Malicious code in advdef01 (PyPI)
The PyPI package advdef01 contained malicious code designed to exfiltrate system information (IP address, username) during installation. The package used a setup.py override to execute the malicious payload when installed.
PyPICompromised packageMalicious commit