Which versions of @deathpoolxrs/dependency-confusion-poc are malicious?

The following npm versions of @deathpoolxrs/dependency-confusion-poc are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @deathpoolxrs/dependency-confusion-poc if I installed it?

Remove @deathpoolxrs/dependency-confusion-poc 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 @deathpoolxrs/dependency-confusion-poc — how do I know if it already compromised me?

If @deathpoolxrs/dependency-confusion-poc 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 @deathpoolxrs/dependency-confusion-poc part of a known attack campaign?

Yes — @deathpoolxrs/dependency-confusion-poc is associated with the RLMA-2026-04709, IN-MAL-2026-009413, RLUA-2026-05848 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 @deathpoolxrs/dependency-confusion-poc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @deathpoolxrs/dependency-confusion-poc (version 1.0.0).

Malicious package

@deathpoolxrs/dependency-confusion-pocnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@deathpoolxrs/dependency-confusion-poc is a confirmed malicious npm package (MAL-2026-7066) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @deathpoolxrs/dependency-confusion-poc (npm)

MAL-2026-7066

Immediate action

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

npm uninstall @deathpoolxrs/dependency-confusion-poc

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

06dc855aafe60352e9cd1ac95678b54228491a6ba210c5593ac73615110b3770

074dc1352aecc512f6de67bd23de8f920559302127e1d6da86a9001a499c6adf

8949c0bb87841a951cebc65bdc775d0bd1434fe307aea3675c0ee82065a3c5ee

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04709IN-MAL-2026-009413RLUA-2026-05848

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @deathpoolxrs/dependency-confusion-poc-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