Which versions of dbgpkg are malicious?

The following PyPI versions of dbgpkg are flagged malicious: 1.3.6, 1.3.7, 1.3.8. Treat any of these as compromised.

How do I remediate dbgpkg if I installed it?

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

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

Yes — dbgpkg is associated with the RLMA-2025-03006, RLUA-2025-06559 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 dbgpkg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dbgpkg (3 malicious versions).

Malicious package

dbgpkgPyPI

Advisory published Jun 18, 2025Updated Dec 24, 2025

dbgpkg is a confirmed malicious PyPI package (MAL-2025-5109) that executes malicious code on install (malicious versions 1.3.6, 1.3.7, 1.3.8). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dbgpkg (PyPI)

MAL-2025-5109

Immediate action

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

pip uninstall dbgpkg

Malicious versions

3 flagged

1.3.61.3.71.3.8

Indicators of compromise (SHA-256)

ad7fc7c34738ac07da72b31e5d8da1330359abd80e4c40ff82b91e7893d424c5

6f67ae6d5301f7790bed5a84f43fe59211c31d52b053dec034acb1339834d8d4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dbgpkg (3 malicious versions).
If you installed it — respond
Remove dbgpkg 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 dbgpkg 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. dbgpkg on PyPI has been identified as a malicious package (versions 1.3.6, 1.3.7, 1.3.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-03006RLUA-2025-06559

References

reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

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