# MAL-2026-17219: Malicious code in nebula-sdk (npm)


- **Type:** Malicious package
- **Package:** `nebula-sdk` (npm)
- **Published:** 28 Sep 2026
- **Also known as:** GHSA-fm5g-6rr8-p9vq

## What is MAL-2026-17219?

MAL-2026-17219 is a malicious package in nebula-sdk, published on 28 Sep 2026. 

### Official description

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.

## What should I do about MAL-2026-17219?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17219 is a malicious package: nebula-sdk (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17219/ (Markdown: https://insights.sbomify.com/MAL-2026-17219/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17219

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17219/
Summaries are generated and may contain mistakes; the official description above is the record.