Malware in @antoncarlos1/nodelamp
Malware was distributed via the npm package @antoncarlos1/nodelamp, resulting in full system compromise of affected installations. The package has been identified and removed from distribution.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @antoncarlos1/nodelamp
The npm package @antoncarlos1/nodelamp contained malware that compromised any system where it was installed or executed. According to the GitHub Security Advisory (GHSA-c3r7-wcqm-j4v8), affected systems should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on compromised computers be rotated immediately from a different, unaffected system. While the malicious package should be removed, the advisory notes that full system control may have been granted to an external entity, meaning removal of the package alone may not eliminate all malicious software introduced by the installation.\n\nThis represents a critical supply chain attack through package distribution, affecting any developer or system that installed or ran this package.
Indicators of compromise
- Packages
- @antoncarlos1/nodelamp
Remediation
- Remove the @antoncarlos1/nodelamp package immediately from all systems
- Rotate all secrets, API keys, and credentials from a clean, unaffected computer
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and access patterns for signs of unauthorized activity during the period the package was installed
- Consider the affected system(s) potentially compromised and plan for full rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-c3r7-wcqm-j4v8 · GitHub Advisory Database
Cite this entry
"Malware in @antoncarlos1/nodelamp." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 3, 2026; last updated July 3, 2026. https://supplychainattack.org/incident/malware-in-antoncarlos1-nodelamp-1k48n4
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 epic-common-node (npm)
The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.
npmCompromised package - containedcritical
Malicious code in epic-common (npm)
The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package - resolvedcritical
Malicious code in epic-sso (npm)
The npm package epic-sso was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.
npmCompromised package - containedcritical
Malicious code in pfp-forms-sme-loan (npm)
The npm package pfp-forms-sme-loan contains malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under well1.site. Any system that imported this package should be considered compromised.
npmCompromised packageMalicious commit