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

nebula-sdknpm

Advisory published Updated

nebula-sdk is a confirmed malicious npm package (MAL-2026-17219) 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 nebula-sdk (npm)

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

What this malware does

The preinstall.cjs lifecycle script embeds a base64-encoded, zlib-compressed Windows PE (~257KB) as a string literal. On npm install, the script decodes and decompresses the blob, writes the resulting executable to %LOCALAPPDATA%\Microsoft\Conhost\conhost.exe (masquerading as the legitimate Windows conhost binary), and spawns it detached with stdio ignored and windowsHide set to true, executing attacker-controlled native code on the installer's Windows machine with no user interaction. Decoded payload strings reference github.com/syskiel/kntrat-e and the IP 65.87.7.132, consistent with a native RAT-family tool. The package's advertised purpose is an AI SDK; a bundled native Windows executable dropped at install time is unrelated to that purpose and is delivered through multi-layer obfuscation (base64 + zlib + string-literal embedding) inside the lifecycle hook.

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)

6173d4941c91c361332072d4542cc10d3cefb945bc40a75ab83e07ffdc2fdb77
f0ca45fda7abd51edfeef37be6d19b4070788180b7625f16354223d81dae4d45
c07b429872f54f5aaad4f0e8e5f456ebac852dc1dcc96a7fa8ffe4b8bf71ee5e

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for nebula-sdk (2 malicious versions).

  2. If you installed it — respond

    Remove nebula-sdk 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 nebula-sdk 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. nebula-sdk 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

GHSA-fm5g-6rr8-p9vqIN-MAL-2026-020586IN-MAL-2026-020592

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

nebula-sdk (npm) malicious package — MAL-2026-17219 | O3 Security