Which versions of faker-py123123thon are malicious?

The following PyPI versions of faker-py123123thon are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate faker-py123123thon if I installed it?

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

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

Yes — faker-py123123thon is associated with the RLMA-2025-05593, GENERIC-standard-pypi-install-pentest, RLUA-2026-00312 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 faker-py123123thon 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 faker-py123123thon (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging faker-py123123thon across your stack and pipelines.

Malicious package

faker-py123123thonPyPI

Malicious code in faker-py123123thon (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191625

Immediate action

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

pip uninstall faker-py123123thon

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

91b4d3f4abf598b219027cd59a3a543942517e437c5067cade4d0dda91ba0ce6

b0ee72045e4466e859b48306aac87effa1034fb74dc3a3d3d11cc7275fa9275d

fab9d41bcbc9a1625b625705433588c2bc1d08ca71e57783cc29b74bc76ddeba

a8149d0dab135babf457bb32a02ff39a7a8b7dca797aaf0af3a7e46c19cdb0b2

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

Campaign

RLMA-2025-05593GENERIC-standard-pypi-install-pentestRLUA-2026-00312

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks faker-py123123thon-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