Which versions of stringhelp are malicious?

The following PyPI versions of stringhelp are flagged malicious: 7.0, 8.0. Treat any of these as compromised.

How do I remediate stringhelp if I installed it?

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

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

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

Search your lockfiles and build artifacts for stringhelp (2 malicious versions).

Malicious package

stringhelpPyPI

Advisory published Apr 18, 2026Updated Apr 18, 2026

stringhelp is a confirmed malicious PyPI package (MAL-2026-2854) that steals credentials and exfiltrates sensitive data (malicious versions 7.0, 8.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stringhelp (PyPI)

MAL-2026-2854

Immediate action

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

pip uninstall stringhelp

What this malware does

The package exfiltrates Discord tokens to a hardcoded location.

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

Campaign: 2026-04-old-stringhelp

Reasons (based on the campaign):

exfiltration-credentials
action-hidden-in-lib-usage

Malicious versions

2 flagged

7.08.0

Indicators of compromise (SHA-256)

614fb208fe0dce0e336281a07696b97a699937b1cb5d6167e6d126e8693b7ae6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for stringhelp (2 malicious versions).
If you installed it — respond
stringhelp 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 stringhelp 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. stringhelp on PyPI has been identified as a malicious package (versions 7.0, 8.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-old-stringhelp

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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