Which versions of randomstringgen are malicious?

The following PyPI versions of randomstringgen are flagged malicious: 0.1, 0.2, 0.3, 0.4. Treat any of these as compromised.

How do I remediate randomstringgen if I installed it?

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

If randomstringgen was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is randomstringgen part of a known attack campaign?

Yes — randomstringgen is associated with the 2026-02-old-randomstringgen 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 randomstringgen across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for randomstringgen (4 malicious versions).

Malicious package

randomstringgenPyPI

Advisory published Feb 28, 2026Updated Feb 28, 2026

randomstringgen is a confirmed malicious PyPI package (MAL-2026-1089) that steals credentials and exfiltrates sensitive data (malicious versions 0.1, 0.2, 0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in randomstringgen (PyPI)

MAL-2026-1089

Immediate action

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

pip uninstall randomstringgen

What this malware does

Using the provided function results in exfiltrating the current running file (likely the user's script) to the hardcoded location.

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

Campaign: 2026-02-old-randomstringgen

Reasons (based on the campaign):

files-exfiltration
action-hidden-in-lib-usage

Malicious versions

4 flagged

0.10.20.30.4

Indicators of compromise (SHA-256)

9fc95ea566ad1938f7f75123eee2d8b3365bf55f06d7aa8a5f569f5e4c696132

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for randomstringgen (4 malicious versions).
If you installed it — respond
randomstringgen 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 randomstringgen was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. randomstringgen on PyPI has been identified as a malicious package (versions 0.1, 0.2, 0.3, 0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-02-old-randomstringgen

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database