Which versions of dpd-security-poc are malicious?

The following npm versions of dpd-security-poc are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate dpd-security-poc if I installed it?

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

If dpd-security-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 dpd-security-poc part of a known attack campaign?

Yes — dpd-security-poc is associated with the RLMA-2026-05041, RLUA-2026-06178 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 dpd-security-poc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dpd-security-poc (version 1.0.0).

Malicious package

dpd-security-pocnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

dpd-security-poc is a confirmed malicious npm package (MAL-2026-7252) 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 dpd-security-poc (npm)

MAL-2026-7252

Immediate action

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

npm uninstall dpd-security-poc

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d7db6054c0a4eae37670dfec2411905d8e1af19d21c9d72232b1d2fde4ce7702

9c33e477364f41eff4458839c3a30873b242df7a491a07e2dea8df50036df32d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dpd-security-poc (version 1.0.0).
If you installed it — respond
Remove dpd-security-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 dpd-security-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. dpd-security-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-05041RLUA-2026-06178

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks dpd-security-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