Which versions of alfooou are malicious?

The following PyPI versions of alfooou are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.4. Treat any of these as compromised.

How do I remediate alfooou if I installed it?

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

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

Yes — alfooou is associated with the RLMA-2024-10965, 2024-10-alfooou, RLUA-2026-00054 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 alfooou 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 alfooou (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging alfooou across your stack and pipelines.

Malicious package

alfooouPyPI

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

MAL-2024-11522

Immediate action

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

pip uninstall alfooou

What this malware does

Running the module triggers obfuscated code that downloads a DLL containing reverse shell and injects it to a benign process.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-10-alfooou

Reasons (based on the campaign):

backdoor
obfuscation

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.4

Indicators of compromise (SHA-256)

094300ca57214363c875154455ee09909af1a73611e5abe001693c03c701bbcf

772fb60c21778086bc9508f874dba7509467cada06e135fa8167be8037a7573b

5bb42c1e46cc4a000429770c7e316646bab8170a9f1191e3f196a4f05a65605f

8ee2f9727c8172c3183bccd30aff7f6ef6af934a16db0b5a5ea3d710e28c213d

eed169b6cdcb77b8d45d9993928ec2ad30c34650aeef4bb18ae8e2f93b23b787

c1acf64b709e06ebdf6de9db6478e491f1ba7760ffa956cd39db0983d9e12a07

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

Campaign

RLMA-2024-109652024-10-alfooouRLUA-2026-00054

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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