Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

api-nebulanpm

Advisory published Updated

api-nebula is a confirmed malicious npm package (MAL-2026-17531) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in api-nebula (npm)

MAL-2026-17531
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall api-nebula

What this malware does

The package declares "preinstall": "node preinstall.cjs" in package.json, and preinstall.cjs is a single-line ~187 KB Function("pbeIUC", "…") invocation implementing a custom PRNG plus string-table decoder (numeric constant table, printable-charset string table UclPgF, a Bob-Jenkins-style mixer, and a decoder that reconstructs strings via modular arithmetic against UclPgF.charCodeAt(...)). The file contains no readable logic — its entire payload is an opaque blob that is decoded and handed to the JS engine during npm install. String fragments visible pre-decoding (e.g. F.kI, [email protected], vCpP.BB/.i+gUAKa) are placeholder-shaped and only resolve to real hosts/commands after runtime decoding, so the actual install-time behavior and any network destinations are hidden from static inspection. The wrapper module (nebula.js) and package.json declare no native build step, no compilation, and no other legitimate reason for a 187 KB obfuscated preinstall script. This is the canonical obfuscated npm preinstall dropper shape: arbitrary attacker-authored code executes on every installer's machine at npm install time, with intent to evade review deliberately concealed by the string-table + Function-eval loader.

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

1 flagged
1.0.0

Indicators of compromise (SHA-256)

b8232ec7756422686c2bce805fc87821e61a5bd9176cdb2fe7c3190fd2b2eae2
630739715b86da1f9f4a6d39d1108dce9965678236516ee34c21ce5ab6f6def5

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for api-nebula (version 1.0.0).

  2. If you installed it — respond

    Remove api-nebula 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 api-nebula 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. api-nebula on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020979GHSA-q4h6-37pw-8pc9

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks api-nebula-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

api-nebula (npm) malicious package — MAL-2026-17531 | O3 Security