Which versions of memtools are malicious?

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

How do I remediate memtools if I installed it?

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

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

Yes — memtools is associated with the RLMA-2025-03646, 2025-07-memlib, RLUA-2026-00513 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 memtools 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 memtools (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 memtools across your stack and pipelines.

Malicious package

memtoolsPyPI

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

MAL-2025-6549

Immediate action

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

pip uninstall memtools

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)

7610337007cb1518ff3ab5fddfce5cdf36a4df92b45d0f389d7e4d333e425780

442cad9234093b04b5d1e1609b4059b82184819bcbcaf06d71e2e11875b18d5e

fafb3bba871c43e80681f3c9f4618ec7547fe2295b120eb93adf31a59bf021f3

c2e5cff183529e337de2e1618244554c8c3d612b7b3383cf24bd2dcead166fe0

c1da537a5e3a142483dd81d21bc6055d761214b7c79c5f50fa2b7c22e1102fab

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 memtools (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 memtools across your stack and pipelines.
If you installed it — respond
memtools 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 memtools 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 memtools 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. memtools 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-036462025-07-memlibRLUA-2026-00513

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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