Which versions of fadlearner are malicious?

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

How do I remediate fadlearner if I installed it?

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

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

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

Malicious package

fadlearnerPyPI

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

MAL-2024-11588

Immediate action

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

pip uninstall fadlearner

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)

baedab409cb9db89ca8ea7d619157796ba152c4b2bc65beaa041d21e822b633b

acc00a365571be0926893ce49493bae7b220faff038154dab42b6527dae6509c

d62336c7b71c148b628034ade6e2ffa9b69ff5e1c593cc29de12f1116f5906e8

63f770dfea4bbc5f89bb2ca367937ea8155dc057af10947ec34a7c4a64e7c35e

a54048cad878e2e7db1039d0b1439307ddbba9605d7e44516bb771a89ae4f2dc

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

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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