@antoncarlos1/nodelampnpm
@antoncarlos1/nodelamp is a confirmed malicious npm package (MAL-2026-6209) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @antoncarlos1/nodelamp (npm)
What this malware does
@antoncarlos1/[email protected] ships a single obfuscated index.js that runs a dropper on require(). The top-level IIFE constructs a hardcoded IPv4 URL by concatenating four numeric literals with '.', issues an HTTPS GET to that bare-IP host, writes the response body to a file under os.tmpdir() with flag 'w+', and immediately spawns it with cwd=os.tmpdir() and windowsHide:true. The module is encoded with obfuscator.io (224-entry RC4 string array, two decoder functions, shuffled control flow) — the only purpose of which is to hide the destination address and the exec edge from reviewers. The package metadata advertises only 'manage the node' with no functionality justifying any network fetch or binary execution, and the package scope (@antoncarlos1) does not match the linked repository owner (guilderguzman). The fetched bytes are unpinned, unverified, and attacker-controlled; any consumer that requires this package (directly or transitively) executes them with the installer's privileges.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @antoncarlos1/nodelamp (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @antoncarlos1/nodelamp across your stack and pipelines.
If you installed it — respond
Remove @antoncarlos1/nodelamp from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @antoncarlos1/nodelamp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @antoncarlos1/nodelamp before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @antoncarlos1/nodelamp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.