NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@antoncarlos1/nodelampnpm

Advisory published Updated

@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)

MAL-2026-6209
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @antoncarlos1/nodelamp

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

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

d930df8b6392b3bbfe3b591d90226374d31fb246e06018521f3f673a815b618a
89db8d7da6352641119e0a7d055b53085d0009dae70f854c0aaaad58a78c9f48
5f4e4ed7d004ae6ffa6701004b19b3a48644adf4b6c8ec54cf9ed56c78b6e449

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @antoncarlos1/nodelamp (2 malicious versions).

  2. 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.

  3. Did it already run?

    If @antoncarlos1/nodelamp was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @antoncarlos1/nodelamp on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007074GHSA-c3r7-wcqm-j4v8IN-MAL-2026-008580

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.

Explore

@antoncarlos1/nodelamp (npm) malicious package — MAL-2026-6209 | O3 Security