Which versions of nebulaai-sdk are malicious?

The following npm versions of nebulaai-sdk are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate nebulaai-sdk if I installed it?

nebulaai-sdk establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed nebulaai-sdk — how do I know if it already compromised me?

If nebulaai-sdk 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.

Is nebulaai-sdk part of a known attack campaign?

Yes — nebulaai-sdk is associated with the IN-MAL-2026-020608 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find nebulaai-sdk across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nebulaai-sdk (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nebulaai-sdk across your stack and pipelines.

Malicious package

nebulaai-sdknpm

nebulaai-sdk is a confirmed malicious npm package (MAL-2026-17228) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nebulaai-sdk (npm)

MAL-2026-17228

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall nebulaai-sdk

What this malware does

The package's preinstall.js contains a base64+zlib-encoded 257 KB Windows PE executable. On npm install on Windows, the script decodes the blob and writes it to %LOCALAPPDATA%\Microsoft\Conhost\conhost.exe — a path and filename that impersonates a legitimate Windows console host binary — then spawns it via child_process.spawn with detached: true, stdio: 'ignore', and windowsHide: true, so execution is silent and survives the npm process. The decoded PE contains a section named .kntrat and references the external host 65.87.7.132 and the repository github.com/syskiel/kntrat-e, indicating remote command-and-control functionality (RAT-shaped naming). The package has no legitimate SDK functionality visible; the preinstall hook exists solely to stage and run the embedded executable. Installing this package on a Windows host results in full arbitrary code execution under the installing user, with a masqueraded persistent binary staged under LOCALAPPDATA and a C2 endpoint reachable at 65.87.7.132.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

dc906b81107141fbd85dcabf89fd2f5112c4e4a134045c90d6a35abb4b67d16e

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nebulaai-sdk (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nebulaai-sdk across your stack and pipelines.
If you installed it — respond
nebulaai-sdk establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If nebulaai-sdk 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 nebulaai-sdk 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

No. nebulaai-sdk 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-020608

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nebulaai-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database