Which versions of @ghost_debugger/nanocache are malicious?

The following npm versions of @ghost_debugger/nanocache are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate @ghost_debugger/nanocache if I installed it?

Remove @ghost_debugger/nanocache 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.

I already installed @ghost_debugger/nanocache — how do I know if it already compromised me?

If @ghost_debugger/nanocache 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 @ghost_debugger/nanocache part of a known attack campaign?

Yes — @ghost_debugger/nanocache is associated with the IN-MAL-2026-017917 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 @ghost_debugger/nanocache 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 @ghost_debugger/nanocache (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ghost_debugger/nanocache across your stack and pipelines.

Malicious package

@ghost_debugger/nanocachenpm

@ghost_debugger/nanocache is a confirmed malicious npm package (MAL-2026-14046) that executes malicious code on install (malicious version 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ghost_debugger/nanocache (npm)

MAL-2026-14046

Immediate action

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

npm uninstall @ghost_debugger/nanocache

What this malware does

On require/import, the package spawns a bundled 1.1 MB Windows executable at vendor/nanocache.exe as a detached background process with stdio ignored, windowsHide set, and child.unref() so it survives parent exit. The declared purpose is an in-memory LRU+TTL cache, which does not require a native background process, and the binary is not built from source shipped in the tarball. Strings inside the executable include /ws/agent, disconnect, update, and exit_code, consistent with a WebSocket-based remote agent that accepts commands from a remote controller. The README further describes vendor/nanocache.exe as a drop-in slot for an arbitrary Windows executable, indicating the npm module functions as a generic launcher for the bundled binary. Installing or importing the package on a Windows host results in an opaque, hidden native process being launched under a cache-library cover story, giving a remote party persistent control over the installer's machine.

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

c027fa29f4577bd052bfda553a617994365ea5855216b877e900610542f4bcce

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ghost_debugger/nanocache (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ghost_debugger/nanocache across your stack and pipelines.
If you installed it — respond
Remove @ghost_debugger/nanocache 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.
Did it already run?
If @ghost_debugger/nanocache 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 @ghost_debugger/nanocache 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. @ghost_debugger/nanocache on npm has been identified as a malicious package (version 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017917

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @ghost_debugger/nanocache-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