Which versions of voodoo-internal-api are malicious?

The following npm versions of voodoo-internal-api are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate voodoo-internal-api if I installed it?

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

If voodoo-internal-api 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 voodoo-internal-api part of a known attack campaign?

Yes — voodoo-internal-api is associated with the RLMA-2026-01830 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 voodoo-internal-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for voodoo-internal-api (version 99.9.9).

Malicious package

voodoo-internal-apinpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

voodoo-internal-api is a confirmed malicious npm package (MAL-2026-2396) that executes malicious code on install (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in voodoo-internal-api (npm)

MAL-2026-2396

Immediate action

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

npm uninstall voodoo-internal-api

What this malware does

The package voodoo-internal-api was found to contain malicious code.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

9c558980012b19d76027f5ccb9a26a195dd7cff2cc4380bbd8180bf2d614feec

a66c21f000ea33496a8cd95744872d47bbd617d4a4cabdae400ae0361cf0faf3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01830

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks voodoo-internal-api-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