Which versions of presudo-generate are malicious?

The following PyPI versions of presudo-generate are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate presudo-generate if I installed it?

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

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

Yes — presudo-generate is associated with the RLMA-2025-00492, 2024-12-langer-updater, RLUA-2026-00604 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 presudo-generate 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 presudo-generate (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging presudo-generate across your stack and pipelines.

Malicious package

presudo-generatePyPI

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

MAL-2025-951

Immediate action

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

pip uninstall presudo-generate

What this malware does

During installation, the package collects quite extensive information about the host and has no other purpose. To avoid detection, the real code is put in a ZIP archive and includes also some VM-detection techniques. The malicious code is activated via metaclass set for the "install" command class in setup.py

Over the time, techniques used in packages are slightly changing, including that some of marked packages don't have malicious part, but rather are used only for tests.

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

Campaign: 2024-12-langer-updater

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.
exfiltration-env-variables
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0419d81ff7fb59e97191bd497f63197ff8031f5b9db1e4a7517be819f3a82c0e

71820f7ce69378e4a84b0ceae0c4547b5e68a9824ce26e836d82e42839a5947c

e390060b9c380a6e7c1743dc35278cbe02801d90678046380344edd73673ca54

ebdaf4c20d1f9fb42f4b196482ac82b879c87a8f85e19002d2df29fa496765ee

9d5cba2287ef708a85a2f716f92a5c3293de02e1167297d082f5a43c1c6b248b

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

Campaign

RLMA-2025-004922024-12-langer-updaterRLUA-2026-00604

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks presudo-generate-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