Which versions of nebula-llm are malicious?

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

How do I remediate nebula-llm if I installed it?

nebula-llm is a typosquat — you almost certainly intended a legitimately-named package. Remove nebula-llm, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed nebula-llm — how do I know if it already compromised me?

If nebula-llm 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 nebula-llm part of a known attack campaign?

Yes — nebula-llm is associated with the IN-MAL-2026-020605 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 nebula-llm 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 nebula-llm (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 nebula-llm across your stack and pipelines.

Malicious package

nebula-llmnpm

nebula-llm is a confirmed malicious npm package (MAL-2026-17227) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nebula-llm (npm)

MAL-2026-17227

Immediate action

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

npm uninstall nebula-llm

What this malware does

The npm package [email protected] ships a preinstall lifecycle script (preinstall.cjs) that embeds a ~257KB Windows PE binary as a base64+zlib-compressed string literal. On npm install on Windows, the script decompresses the blob, writes it to %LOCALAPPDATA%\Microsoft\Conhost\conhost.exe — impersonating the legitimate Windows Console Host binary — and spawns it detached with stdio ignored and windowsHide:true, then unrefs the child so it survives the install process. The decoded PE contains a.kntrat section and references github.com/syskiel/kntrat-e and IP 65.87.7.132, consistent with a persistent remote-access implant. Installation therefore executes an opaque author-supplied executable on the installer's host with no user interaction and no purpose related to any documented package function.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b33da6aef41209f654f8f76cc56074a7b827599f42f941e3917326da1f4d2566

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nebula-llm (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 nebula-llm across your stack and pipelines.
If you installed it — respond
nebula-llm is a typosquat — you almost certainly intended a legitimately-named package. Remove nebula-llm, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If nebula-llm 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 nebula-llm 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. nebula-llm 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-020605

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nebula-llm-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database