Which versions of makronlox are malicious?

The following PyPI versions of makronlox are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate makronlox if I installed it?

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

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

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

Malicious package

makronloxPyPI

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

MAL-2025-191646

Immediate action

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

pip uninstall makronlox

What this malware does

Package automatically download and runs an executable, which then imitates a malicious action and requests ransom payment.

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

Campaign: 2025-10-makronlox

Reasons (based on the campaign):

Downloads and executes a remote executable.

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

47be8a7e5f1940d95c2347fecd3bb6c7f27e108baa8e7d05164057ab477e35a1

17abd14fe59573528e2f3cb5f17962f31547b060a04b3ba386d914ee0a2da190

f918d3ae448737e8a58e16ad57af3037e27ba8ab02fef22ba6e0b4f6f2c49e1a

972236288ab417e0cd3764ea452ba8812663a2ea575fffbc47bc34d4c9387d63

a8e8182c2a32d7548945d394510b18fc41147847c423b9ebbcd7c17a2fa37d9e

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

Campaign

RLMA-2025-056182025-10-makronloxRLUA-2026-00488

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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