Which versions of awesome-tools-collection are malicious?

The following PyPI versions of awesome-tools-collection are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6. Treat any of these as compromised.

How do I remediate awesome-tools-collection if I installed it?

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

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

Yes — awesome-tools-collection is associated with the RLMA-2025-04745, 2025-08-learning-pypi-demo-nisimi, RLUA-2026-00126 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 awesome-tools-collection 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 awesome-tools-collection (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging awesome-tools-collection across your stack and pipelines.

Malicious package

awesome-tools-collectionPyPI

Malicious code in awesome-tools-collection (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47746

Immediate action

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

pip uninstall awesome-tools-collection

What this malware does

Installing packages exfiltrates data (different in different packages and versions) or run revshells

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

Campaign: 2025-08-learning-pypi-demo-nisimi

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
exfiltration-generic

Malicious versions

7 flagged

0.1.00.1.10.1.20.1.30.1.40.1.50.1.6

Indicators of compromise (SHA-256)

fdf85e89ad8e719ea161ef629b069744f958239bc89f4b0131ecd641a7fe37d7

88262de451d7eb0b85f040386be49fbed3622a503eed18d3e2af1d8d91921afd

1b8c27c2c5512bcb412c63a9e5ab3a392cb21f8ff51f281d8e7ac73a08929abb

35787e4b8050da40f613d4d0741f82f0793388b360393758954c6ae6f0d406d3

506219c146fcc0f77e004675ffc2d6aae316ea1f3514eda6223ce74de6aade34

4d88e9bf230c35f5cc5a093f9e7d1a6490a7464bf5c81ee6ff170c7e5baed3f6

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

Campaign

RLMA-2025-047452025-08-learning-pypi-demo-nisimiRLUA-2026-00126

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks awesome-tools-collection-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