Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

user-gen-agent-randomPyPI

Malicious code in user-gen-agent-random (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11738
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall user-gen-agent-random

What this malware does

Inside the library there is a part running code hidden in the attached image, which then exfiltrate user-provided data, downloads and install next stage code, exfiltrate TXT files and finally installs infostealers - Lumma and a custom one. Arround L110

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

Campaign: 2024-10-fake-usreagent

Reasons (based on the campaign):

  • infostealer

  • files-exfiltration

  • clipboard-stealing

  • obfuscation

  • clones-real-package

  • action-hidden-in-lib-usage

Malicious versions

3 flagged
1.6.81.6.91.7.0

Indicators of compromise (SHA-256)

d654bb7f8b02092a700d5d50271a1084cbb40675f2b37fbc73a31c1ff0acc700
41554d5e5b4ef559940a404c71e2a4b8fc03c2933fc5a66fd0ac644c6b8ab542
22f729ba6b5abecacd2d94214cf0075ac0729fb59d4e9cc1cf6287a2bf6e2ab6
017b8528e013ac05af3886e43b02de2437efabcc7944fd7cdfe28dfe56b8a0b0
09f7850df7ff22eaf03f4d6790d4f0ef1a725b058221b417be36173fda6b6a9e
ed29bfc65da02c76aa12dc5a9c13e0aed560f55091bca93be2bb4a5053ab0a9b

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for user-gen-agent-random (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging user-gen-agent-random across your stack and pipelines.

  2. If you installed it — respond

    user-gen-agent-random 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.

  3. Did it already run?

    If user-gen-agent-random 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.

  4. How O3 protects you

    O3 blocks user-gen-agent-random 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. user-gen-agent-random on PyPI has been identified as a malicious package (versions 1.6.8, 1.6.9, 1.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-111992024-10-fake-usreagentRLUA-2026-00874

References

Credits

  • Kamil Mańkowski (kam193)
  • ReversingLabs · finder

Detect & block this

O3 blocks user-gen-agent-random-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
user-gen-agent-random (PyPI) malicious package — MAL-2024-11738 | O3 Security