Which versions of aslmutetion are malicious?

The following PyPI versions of aslmutetion are flagged malicious: 98.7, 99.7. Treat any of these as compromised.

How do I remediate aslmutetion if I installed it?

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

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

Yes — aslmutetion is associated with the RLMA-2024-10973, 2024-11-byted-dast, RLUA-2026-00079 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 aslmutetion 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 aslmutetion (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aslmutetion across your stack and pipelines.

Malicious package

aslmutetionPyPI

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

MAL-2024-11529

Immediate action

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

pip uninstall aslmutetion

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

Malicious versions

2 flagged

98.799.7

Indicators of compromise (SHA-256)

7529bb9d685cae2a9198235e133a1a443d170630d4772a610f77b81d9ff57056

b3ff8433027bd75abdb1eaace3cb80b77c52cd03a4dbfd55341177aeb0783f3f

c052a3699080e1fef9f2799c9b4bd850eedd75f5fca1a3ea0dce97607fce9e49

152efe3977a6e1dc8481d375b5ec352c1f72c1a5d9d4e3ebaf9b977a868eb1fd

c4fe6901748ea11dcd8a4bf6ef906ef78b6299b5724d4816bbc30c565e9e1ee2

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

Campaign

RLMA-2024-109732024-11-byted-dastRLUA-2026-00079

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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