Which versions of ghost-module are malicious?

The following npm versions of ghost-module are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate ghost-module if I installed it?

Remove ghost-module 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-module — how do I know if it already compromised me?

If ghost-module 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.

Is ghost-module part of a known attack campaign?

Yes — ghost-module is associated with the RLMA-2026-01766 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-module across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ghost-module (version 99.0.0).

Malicious package

ghost-modulenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

ghost-module is a confirmed malicious npm package (MAL-2026-2366) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ghost-module (npm)

MAL-2026-2366

Immediate action

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

npm uninstall ghost-module

What this malware does

The package ghost-module was found to contain malicious code.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

de2bf5fcae31b0deb78a07adda9b24c41706d65206f4ee70ec1a33e16db178e9

67b6330e4cf0d3fdd5e5809026b2bf763eb9e40677d38cca3a39af3a079d265f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ghost-module (version 99.0.0).
If you installed it — respond
Remove ghost-module 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-module 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. ghost-module on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01766

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ghost-module-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