Which versions of fedlearnerr are malicious?

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

How do I remediate fedlearnerr if I installed it?

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

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

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

Malicious package

fedlearnerrPyPI

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

MAL-2024-11592

Immediate action

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

pip uninstall fedlearnerr

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)

a809cdcdadba43947f01600727f6ce980aefebf17ecc66e7b8aa1ca3533e2120

e6a698599de7db18de994bae5b364780166c4c1cc99f780ebb7c79e005710222

6a1b34e827701fe018f65d1cdb84113641d91137ad8fff24de2b50f84f94d889

908bae4c06755ad8a8e4aec63751bbfffacf4961bfd65c0fc68ab1aa412b8fa0

ddf6b578ec1373d5ad599716dcb8a23ef15462d0c1102a1d39d31db78201eb2d

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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