Which versions of manifest-confusion-poc-audit are malicious?

The following npm versions of manifest-confusion-poc-audit are flagged malicious: 999999999.999999999.999999999. Treat any of these as compromised.

How do I remediate manifest-confusion-poc-audit if I installed it?

Remove manifest-confusion-poc-audit 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 manifest-confusion-poc-audit — how do I know if it already compromised me?

If manifest-confusion-poc-audit 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 manifest-confusion-poc-audit part of a known attack campaign?

Yes — manifest-confusion-poc-audit is associated with the RLMA-2026-01426 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 manifest-confusion-poc-audit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for manifest-confusion-poc-audit (version 999999999.999999999.999999999).

Malicious package

manifest-confusion-poc-auditnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

manifest-confusion-poc-audit is a confirmed malicious npm package (MAL-2026-1790) that executes malicious code on install (malicious version 999999999.999999999.999999999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in manifest-confusion-poc-audit (npm)

MAL-2026-1790

Immediate action

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

npm uninstall manifest-confusion-poc-audit

What this malware does

The package manifest-confusion-poc-audit was found to contain malicious code.

Malicious versions

1 flagged

999999999.999999999.999999999

Indicators of compromise (SHA-256)

f14577d0e24ac0386f40d3c18ca8c242a177f0add4958472b1f1b8738fd92696

bdce3a4402dab0a3cd3ccff6522e439711936fb0c4077ea260dde4b8392cddc1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01426

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks manifest-confusion-poc-audit-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