Which versions of my-fun-tools are malicious?

The following PyPI versions of my-fun-tools are flagged malicious: 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate my-fun-tools if I installed it?

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

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

Yes — my-fun-tools is associated with the RLMA-2025-03649, 2025-06-my-fun-tools, RLUA-2026-00547 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 my-fun-tools 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 my-fun-tools (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging my-fun-tools across your stack and pipelines.

Malicious package

my-fun-toolsPyPI

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

MAL-2025-6552

Immediate action

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

pip uninstall my-fun-tools

What this malware does

During installation, the obfuscated code attempts to insert a modified Python DLL and runs a code.

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

Campaign: 2025-06-my-fun-tools

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation

Malicious versions

2 flagged

0.1.10.1.2

Indicators of compromise (SHA-256)

f8229907a1c2b8e9a4d1013f6bf6232b3bf902a4b93a2a5750a0b8b95cf18355

2b06bd8806e27153d3e50bfa9d87e1de02e33d2dbf117494f1c37cf318f6a253

6642f3653e49e0a80b7fadf4c06bc64cba8a1a359772f1c7a668888278348fd6

c5bae316cd4e800afec4b840d75d5ff19324781ce4f0a9e754f2784ff6eeabf0

36c03149cb1df8b6d2546233fe74412f04b4b7a4f45da6b9d3c385b1a2c4b636

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

Campaign

RLMA-2025-036492025-06-my-fun-toolsRLUA-2026-00547

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks my-fun-tools-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