Which versions of manojmacpy are malicious?

The following PyPI versions of manojmacpy are flagged malicious: 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8. Treat any of these as compromised.

How do I remediate manojmacpy if I installed it?

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

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

Yes — manojmacpy is associated with the RLMA-2024-08495, RLUA-2024-11084, GENERIC-standard-pypi-install-pentest, RLUA-2026-00495 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 manojmacpy 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 manojmacpy (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging manojmacpy across your stack and pipelines.

Malicious package

manojmacpyPyPI

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

MAL-2024-10040

Immediate action

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

pip uninstall manojmacpy

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

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.

Malicious versions

8 flagged

1.1.11.1.21.1.31.1.41.1.51.1.61.1.71.1.8

Indicators of compromise (SHA-256)

ff96cc713ce727f0734abe0471b4ba7a1fd47863caee5e805b2467f48762ce5d

a24dae982ba21eb910537256443fe2a3f61bf8eb13cf7f348392387a9430a568

6b7616e22978cfcda1c9542f632996b2cbcf3c81db20b69fb22bc604e4727534

bbbe44a9dde17f1de0f817f7d4756cc23260eaad55133199b34cabe42e378bf5

43f698a82478f2ac97f22747beb9861f1744145f88e0c7c9943f0b911da6ef16

2141859207d24d904187e0de82dfa8c140b903d974e585080ba885a3c75a5747

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

Campaign

RLMA-2024-08495RLUA-2024-11084GENERIC-standard-pypi-install-pentestRLUA-2026-00495

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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