Malware in @404c3s4r/testxxx
Malware was discovered in the npm package @404c3s4r/testxxx. Systems with this package installed or running are considered fully compromised, requiring immediate secret rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @404c3s4r/testxxx
A malicious npm package, @404c3s4r/testxxx, was identified and published on GitHub's advisory database. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. All secrets and cryptographic keys stored on affected systems must be rotated immediately from a different, uncompromised computer.\n\nWhile the package should be removed, complete remediation is not guaranteed due to the level of system compromise. Additional malicious software may persist even after package removal.\n\nAffected users should treat their systems as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- @404c3s4r/testxxx
Remediation
- Immediately remove the @404c3s4r/testxxx package from all systems
- Rotate all secrets, API keys, and cryptographic credentials from a different, uncompromised computer
- Perform a full security audit and malware scan of affected systems
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical
- Review access logs and audit trails for any unauthorized activity during the period the package was installed
- Notify relevant stakeholders and security teams of the compromise
Sources
- GitHub Advisory GHSA-hc67-hjfq-hpff · GitHub Advisory Database
Cite this entry
"Malware in @404c3s4r/testxxx." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 30, 2026; last updated July 30, 2026. https://supplychainattack.org/incident/malware-in-404c3s4r-testxxx-iavdq6
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in modern-localization (npm)
The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-tax (npm)
The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package