What does the mecit3 malware do?

Package uses the template from https://github.com/thegoodhackertv/malpip to explore building malicious PyPI packages. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: SCRIPT_KIDDIE-thegoodhacker-paquete 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. - The package overrides the install command in setup.py to execute malicious code during installation. - Package uses simple pre-prepared tools to create a low-quality malicious action.

Which versions of mecit3 are malicious?

The following PyPI versions of mecit3 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate mecit3 if I installed it?

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

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

Yes — mecit3 is associated with the RLMA-2024-08508, SCRIPT_KIDDIE-thegoodhacker-paquete, RLUA-2026-00509 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 mecit3 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 mecit3 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mecit3 across your stack and pipelines.

Malicious package

mecit3PyPI

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

MAL-2024-10044

Immediate action

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

pip uninstall mecit3

What this malware does

Package uses the template from https://github.com/thegoodhackertv/malpip to explore building malicious PyPI packages.

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

Campaign: SCRIPT_KIDDIE-thegoodhacker-paquete

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.
The package overrides the install command in setup.py to execute malicious code during installation.
Package uses simple pre-prepared tools to create a low-quality malicious action.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

240b5ff648f6cedf87b383c5e8c508b812b285d46d7ebe4eeb5da793de384dce

4023e69dfea6e0bbb8dcabbde24d44e9ada9d2f109ebf0cf7ba5111a8b108638

3b0998e3b9d6f9e46cd475fa5a18c38a48f7e3e72d02350d7431375fad7dd871

829e6f2c9bad1f83f7e7bc433359b7242a786df7e9631c40197e17c403a42d83

8cb8fe7af2d559fde1af2f461c001dab0d639b9c537ca8049b00aa51353e1200

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

Campaign

RLMA-2024-08508SCRIPT_KIDDIE-thegoodhacker-paqueteRLUA-2026-00509

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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