Which versions of simple-mali-pkg are malicious?

The following PyPI versions of simple-mali-pkg are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate simple-mali-pkg if I installed it?

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

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

Yes — simple-mali-pkg is associated with the RLMA-2025-03684, RLUA-2025-04256, 2025-07-0x9xnx, RLUA-2026-00759 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 simple-mali-pkg 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 simple-mali-pkg (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging simple-mali-pkg across your stack and pipelines.

Malicious package

simple-mali-pkgPyPI

Malicious code in simple-mali-pkg (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6585

Immediate action

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

pip uninstall simple-mali-pkg

What this malware does

Series of packages mostly with an obfuscated infostealer attempting to collect Chrome data. While discord webhook is usually set to an example, there are other, correct uploading URLs

Some of related packages only test partial malicious code, like webhooks from overwritten setup.py

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

Campaign: 2025-07-0x9xnx

Reasons (based on the campaign):

infostealer
obfuscation
exfiltration-browser-data
exfiltration-crypto
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

4960d2daee9d0783b20f5190a62ad7fb80928cf4435629e391b70c4ca6d76efc

495fed0bd11ecd2b387f276a9b2236ff40501bd7601670a9fdcfe8e816415f1a

666dea08a29c207ca63db07646ff8d431dbe7aa59721307dd6367c594e01e4e9

c9629656d765c03a690cd0d32598fac52e66c8f5c82dae9405280ee04e1b0280

42e09931ca46089e564a937e3fefaf4e23492e2e1b8c8efbdb8caef061358d54

d1cdb7da5c9c1a2f04e38e4db3bf8023b5cee4fcdb3c408dc0073ca4de525a74

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

Campaign

RLMA-2025-03684RLUA-2025-042562025-07-0x9xnxRLUA-2026-00759

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks simple-mali-pkg-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