Which versions of mainx are malicious?

The following PyPI versions of mainx are flagged malicious: 0.1, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 1, 1.0. Treat any of these as compromised.

How do I remediate mainx if I installed it?

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

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

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

Malicious package

mainxPyPI

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

MAL-2025-6540

Immediate action

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

pip uninstall mainx

What this malware does

While described as educational package to simulate post-exploitation environment, the malware is active and once started, automatically attempts to exfiltrate sensitive data (credentials, cookies, etc.) and places a Discord implant. The remote target is hard coded in the code.

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

Campaign: 2025-06-mainx

Reasons (based on the campaign):

obfuscation
infostealer
files-exfiltration
exfiltration-credentials
exfiltration-browser-data
peristence-autorun
The package contains code to detect if it is running in a sandbox environment.

Malicious versions

9 flagged

0.10.40.50.60.70.80.911.0

Indicators of compromise (SHA-256)

c47485e969c40c9ce7c118d971f25ff7bbcf66f6d961a28ffa39d7bf497957d3

7f7a6cb96cd1bab4f33b465ea33076403d7c65d54b346d865a57eb11ee2fd712

e24c50cb97b2294bf6202850b4bc869265cf991422d480d67db0e89f807fa45e

6a77aad2f42165ec9582f04fffab948f6a1125564e34f4d09c8d089b2708d8d2

6f37d98ee668c0690e6163289206307f8b89b3af36f23b6245eaa22b141110f7

0e2991d8b172137fed549d6f6671dfd4a38ef4c0e6e09a906908c0232e28e33e

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

Campaign

RLMA-2025-03634RLUA-2025-041942025-06-mainxRLUA-2026-00487

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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