Which versions of discorddox are malicious?

The following PyPI versions of discorddox are flagged malicious: 0.1.8, 1.8.8. Treat any of these as compromised.

How do I remediate discorddox if I installed it?

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

If discorddox was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is discorddox part of a known attack campaign?

Yes — discorddox is associated with the RLMA-2025-03009, 2025-05-telegramdoxing, RLUA-2026-00272 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 discorddox across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for discorddox (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging discorddox across your stack and pipelines.

Malicious package

discorddoxPyPI

Malicious code in discorddox (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-5112

Immediate action

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

pip uninstall discorddox

What this malware does

The package contains an embedded malicious executable (probably blank grabber) started when running the module.

Probably continuation of 2025-05-pydoxing

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

Campaign: 2025-05-telegramdoxing

Reasons (based on the campaign):

infostealer
infostealer:blankgrabber

Malicious versions

2 flagged

0.1.81.8.8

Indicators of compromise (SHA-256)

8f20e1e13eb3beb82587d2a2600323bc893176e78b3ef020ca41c75e04a63b19

b4c2a07c246c68560539fffa5e862c67358e50b41ef0e1d5060547bf6281d6ac

52f656f62a0fe1e90282cf7e8004bfd78e69a854e5e7a9c33ef72b7e5b43b831

15b3247cdc9971093df59eca596defad5dcaf64905671a595b558b4c8fc4d761

ec93fe04987030f2fc9ebe288e48e22a0fd265eb51f687844ccce95360e49b25

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for discorddox (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging discorddox across your stack and pipelines.
If you installed it — respond
discorddox 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 discorddox was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks discorddox before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. discorddox on PyPI has been identified as a malicious package (versions 0.1.8, 1.8.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-030092025-05-telegramdoxingRLUA-2026-00272

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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