@antoncarlos1/nodelamp (npm) · Malicious Code
Affects @antoncarlos1/nodelampSource GCVE Database
Malicious package : remove @antoncarlos1/nodelamp and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 15:56 UTC
Malicious package
Published to npm · OSV MAL-2026-6209
What to do
Remove @antoncarlos1/nodelamp from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@antoncarlos1/nodelamp | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d930df8b6392b3bbfe3b591d90226374d31fb246e06018521f3f673a815b618a) @antoncarlos1/nodelamp@1.0.1 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. ## Source: ghsa-malware (89db8d7da6352641119e0a7d055b53085d0009dae70f854c0aaaad58a78c9f48) 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.