Which versions of easyaillm2 are malicious?

The following PyPI versions of easyaillm2 are flagged malicious: 2.0.16, 2.0.17, 2.0.18, 2.0.67, 2.0.68. Treat any of these as compromised.

How do I remediate easyaillm2 if I installed it?

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

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

Yes — easyaillm2 is associated with the 2026-06-easyaillm, IN-MAL-2026-006665, IN-MAL-2026-006664 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 easyaillm2 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 easyaillm2 (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging easyaillm2 across your stack and pipelines.

Malicious package

easyaillm2PyPI

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

MAL-2026-5765

Immediate action

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

pip uninstall easyaillm2

What this malware does

On pip install easyaillm2, setup.py fetches a raw text body from https://pastebin.com/raw/yBcUM1QB and passes the first line directly to os.system('cmd /c "..."'), executing whatever the mutable, anonymous Pastebin paste currently serves with the installer's privileges. There is no integrity check, no version pinning, and no relationship between the destination and any legitimate publisher. The package itself ships no module code (the source tree contains only egg-info), and its name/description mimic LLM-tooling naming (easyaillm2 / easyllama2) — the install-time Pastebin dropper is the package's only behavior. A Pastebin owner can swap the payload at any moment, turning every future pip install of this version into arbitrary remote code execution on the installer's machine.

During installation, the code attempts to download and start a malicious executable.

Likely related to 2025-08-raknet-testing-package.

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

Campaign: 2026-06-easyaillm

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware
tool:mshta

Malicious versions

5 flagged

2.0.162.0.172.0.182.0.672.0.68

Indicators of compromise (SHA-256)

44a9d76b87fed91bba537f979b2d6f63a7e1758c73424b2d3ffd47bffefe6761

53c3db7e10b21fbb047f524710f5d19dd52decd68dbc91029d35ff5378974f98

f532239be50513698758c81009444ff49bcf4a140fab11734107d81c4eab6684

9c1e32160bfefa9aabd05f8d93dd0172b0d00dde9bfbae45fb1589932e7f618b

a312943656e5a64fc0631e40efd28a69dd11314c1cc6207fa893b65bf03ec9ca

55831f4426da4aebb6f20ccdd7af6ba0f9a4c847dd92a0a1c3c8e2ad99a11554

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

Campaign

2026-06-easyaillmIN-MAL-2026-006665IN-MAL-2026-006664

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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