Which versions of fredmi are malicious?

The following PyPI versions of fredmi are flagged malicious: 3.9. Treat any of these as compromised.

How do I remediate fredmi if I installed it?

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

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

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

Malicious package

fredmiPyPI

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

MAL-2023-3576

Immediate action

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

pip uninstall fredmi

What this malware does

EsqueleSquad group published nearly 6000 malicious PyPi and NPM packages, executing spyware and information-stealing malware

Malicious versions

1 flagged

3.9

Indicators of compromise (SHA-256)

01c99c53e4554cc5799b0b94a6bd72836ccf768e513a2b299ccdc4d963603df6

4641dfc768fcb3c4d7ea07d23959b8383c1334cb04814e83ce937df6dc7271dd

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

Campaign

RLMA-2024-03943

References

medium.com

Credits

Checkmarx · finder
ReversingLabs · finder

Detect & block this

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