Which versions of py-stringlibencode are malicious?

Every published version of py-stringlibencode on PyPI is considered malicious. Remove the package entirely.

How do I remediate py-stringlibencode if I installed it?

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

If py-stringlibencode 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.

How do I find py-stringlibencode across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for py-stringlibencode (all published versions).

Malicious package

py-stringlibencodePyPI

py-stringlibencode is a confirmed malicious PyPI package (MAL-2023-5634) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in py-stringlibencode (PyPI)

MAL-2023-5634

Immediate action

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

pip uninstall py-stringlibencode

What this malware does

EsqueleSquad group published nearly 6000 malicious PyPi and NPM packages, executing spyware and information-stealing malware

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

ebc46531bce903529f16f923b57650d8247de07eb0745c52451a7e6f5a124e02

Detection & response playbook

Credential / info stealer

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

References

medium.com

Credits

Checkmarx · finder

Detect & block this

O3 blocks py-stringlibencode-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