Which versions of fedlearnre are malicious?

The following PyPI versions of fedlearnre are flagged malicious: 912.6. Treat any of these as compromised.

How do I remediate fedlearnre if I installed it?

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

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

Yes — fedlearnre is associated with the RLMA-2024-11044, 2024-11-byted-dast, RLUA-2026-00317 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 fedlearnre 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 fedlearnre (version 912.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fedlearnre across your stack and pipelines.

Malicious package

fedlearnrePyPI

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

MAL-2024-11593

Immediate action

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

pip uninstall fedlearnre

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

Malicious versions

1 flagged

912.6

Indicators of compromise (SHA-256)

bb505d90722c5ff38ab78ca88bfb9c0142e1411165c00f2a830c638da329bd90

1966a3b16d418c04b279a6a1c825a3b78a0bd5875df62a32a4e66991d67ec9e1

cbc005ae139aa93da4c4f580aaef573edfee5f079036ff5989a8974a15d3cb14

a4f2515c0c9ef4da0e391fa8664e49413fb6156ae1d0c793f029d8fd6605ee50

f57f7d60e5a5726d4e69b19be073451fdc7292d75d78448148beec23fee0012e

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

Campaign

RLMA-2024-110442024-11-byted-dastRLUA-2026-00317

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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