Which versions of fredli are malicious?

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

How do I remediate fredli if I installed it?

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

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

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

Malicious package

fredliPyPI

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

MAL-2023-3575

Immediate action

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

pip uninstall fredli

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)

3d49716b05f951243dfb12ab8ce3d149d9ea2201c95309c1795c1a80bb13797a

0afa7123bec1e72c08204ae553b02a323b948eb59f7118d07cd42cf3315535c9

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 fredli (version 3.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fredli across your stack and pipelines.
If you installed it — respond
fredli 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 fredli 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 fredli 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. fredli 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-03942

References

medium.com

Credits

Checkmarx · finder
ReversingLabs · finder

Detect & block this

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