Which versions of telegramdoxing are malicious?

The following PyPI versions of telegramdoxing are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate telegramdoxing if I installed it?

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

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

Yes — telegramdoxing is associated with the 2025-05-telegramdoxing 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 telegramdoxing 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 telegramdoxing (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging telegramdoxing across your stack and pipelines.

Malicious package

telegramdoxingPyPI

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

MAL-2025-191888

Immediate action

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

pip uninstall telegramdoxing

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

1 flagged

0.1.0

Indicators of compromise (SHA-256)

c633ea245398c5eee464ce4de052ff892074a3697a2fd03419d82fd3026ffba5

4cdffd265ab7e5d199258a068bf6c251370ae931fc905109bd2fb659cd7d9114

c2c1dbf6a62df14bd6ece87af741c302a45dbe41baa397d9e472b2a71b5a58e5

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 telegramdoxing (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging telegramdoxing across your stack and pipelines.
If you installed it — respond
telegramdoxing 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 telegramdoxing 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 telegramdoxing 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. telegramdoxing on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-05-telegramdoxing

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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