Which versions of wraith-module are malicious?

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

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

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

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

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

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

Malicious package

wraith-modulenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

wraith-module is a confirmed malicious npm package (MAL-2026-2397) 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 wraith-module (npm)

MAL-2026-2397

Immediate action

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

npm uninstall wraith-module

What this malware does

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

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

26696a74b2af8683e2e2a4afaa24ca4bffcf81b15edc63afc63f9001ed819b81

9e01edc3106b7a83dd7050b7ade8ef141a38fac23b8829ed8d2f4e1f1402829b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for wraith-module (version 99.0.0).
If you installed it — respond
Remove wraith-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 wraith-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. wraith-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-01834

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks wraith-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