Which versions of osint-tool are malicious?

The following PyPI versions of osint-tool are flagged malicious: 0.1, 0.2, 0.4, 0.5. Treat any of these as compromised.

How do I remediate osint-tool if I installed it?

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

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

Yes — osint-tool is associated with the 2024-09-discord-token-lib 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 osint-tool 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 osint-tool (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging osint-tool across your stack and pipelines.

Malicious package

osint-toolPyPI

Malicious code in osint-tool (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12320

Immediate action

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

pip uninstall osint-tool

What this malware does

osint packages promise to be OSINT tool, however, when providing the username to search for, the package attempts to exfiltrate Discord tokens from the user.

The original package suggests being a library for Discord exfiltration, what is suspicious on its own, but in addition, the entry point located in main.py exfiltrate local Discord tokens to a hardcoded webhook.

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

Campaign: 2024-09-discord-token-lib

Reasons (based on the campaign):

exfiltration-generic
action-hidden-in-lib-usage

Malicious versions

4 flagged

0.10.20.40.5

Indicators of compromise (SHA-256)

0d5c4163ca79428423dab39798608ee8cc3f01459134f4ebaaa304b7707bd43e

10a834a37294b0f3aaf52345444f8c5c2a15dde780c8342446c53ecc05d623c0

021db96fc63001447434cd54e4264a624c68527ba98de376627ee718e26f52ce

b1826528a64b1a5d346db7a26ccf0ee6de648d2542ea1244040cc644c625ac69

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

Campaign

2024-09-discord-token-lib

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks osint-tool-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