Which versions of memlib are malicious?

The following PyPI versions of memlib are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate memlib if I installed it?

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

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

Yes — memlib is associated with the RLMA-2025-03644, 2025-07-memlib, RLUA-2026-00511 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 memlib 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 memlib (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging memlib across your stack and pipelines.

Malicious package

memlibPyPI

Malicious code in memlib (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6547

Immediate action

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

pip uninstall memlib

What this malware does

Installing the package triggers a code that looks like downloading a picture, but in fact downloads and starts an executable with malware. Note that file supplied from the URL differs depending on the presence of the special header

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

Campaign: 2025-07-memlib

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

e424a3ccba21168bc30bb897ea5eb6e2943ee8a5554c39eec55f049031239127

de3ef8a2a725d846e8066394b238be79bfe0d7b7e7c3b653dc1b5e7dc12361d2

a0d0e362d3ea9b768078a9e47f80c667acef799c7099f8044e74fd1738fdedb4

d5e00072c0ca596f2cfeffed47046624395c7ae0158ae4df3ef306239b6109f8

3824a3e69aad7c7ad9b98554d431c114976015a7766187d94716b68048cc4f45

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

Campaign

RLMA-2025-036442025-07-memlibRLUA-2026-00511

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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