Which versions of agent-user-generate are malicious?

The following PyPI versions of agent-user-generate are flagged malicious: 1.6.7. Treat any of these as compromised.

How do I remediate agent-user-generate if I installed it?

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

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

Yes — agent-user-generate is associated with the RLMA-2024-10960, 2024-10-fake-usreagent, RLUA-2026-00037 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 agent-user-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 agent-user-generate (version 1.6.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging agent-user-generate across your stack and pipelines.

Malicious package

agent-user-generatePyPI

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

MAL-2024-11517

Immediate action

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

pip uninstall agent-user-generate

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

1 flagged

1.6.7

Indicators of compromise (SHA-256)

a889abb4eadea57db9003ed22341c12187f6d456fac6224fe735a678cd576e9d

177a51807e8613299d7d6c39332f6b1c0ceb742b4f7e438ede97de877efc65c6

514af1dfd929068fabc7527812b99ec6a287c3601d7cf4ed1d29c55e74339fac

e581ab4a4b611e076da1c25ad0fb0e77b1c47c5af132617d70184311e7fffd23

029202de1000a3da43e4a8f64421173d0e4ad674efd9ff01e42539fd81031f67

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

Campaign

RLMA-2024-109602024-10-fake-usreagentRLUA-2026-00037

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks agent-user-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