Which versions of doxer are malicious?

The following PyPI versions of doxer are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate doxer if I installed it?

doxer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed doxer — how do I know if it already compromised me?

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

Yes — doxer is associated with the RLMA-2025-04760, 2025-08-doxer, RLUA-2026-00282 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 doxer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for doxer (version 0.1).

Malicious package

doxerPyPI

Advisory published Sep 2, 2025Updated Mar 19, 2026

doxer is a confirmed malicious PyPI package (MAL-2025-47759) that steals credentials and exfiltrates sensitive data (malicious version 0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in doxer (PyPI)

MAL-2025-47759

Immediate action

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

pip uninstall doxer

What this malware does

During installation a screenshot is exfiltrated, and the package has no other purpose

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-08-doxer

Reasons (based on the campaign):

other
exfiltration-generic

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

793b761f2d49cbb0e7513960694528737a0c16e1d8dbbae50af32220680386e9

bcfc40e7e541243960da4c78812a8fbee204a120b4195f4df25b6a89ea2053ab

5e6e78428567e3ac4f2fdc27911858b6758446b4fe60c754488f881a203e32a9

39e21cdb7c3204b73028960631553c340c3b267625eb0c2ce68061907794de7e

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for doxer (version 0.1).
If you installed it — respond
doxer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If doxer 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. doxer on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-047602025-08-doxerRLUA-2026-00282

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks doxer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database