Which versions of masirkhan are malicious?

The following PyPI versions of masirkhan are flagged malicious: 0.1.9. Treat any of these as compromised.

How do I remediate masirkhan if I installed it?

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

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

Yes — masirkhan is associated with the RLMA-2025-00484, GENERIC-standard-pypi-install-pentest, RLUA-2026-00498 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 masirkhan 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 masirkhan (version 0.1.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging masirkhan across your stack and pipelines.

Malicious package

masirkhanPyPI

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

MAL-2025-944

Immediate action

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

pip uninstall masirkhan

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

1 flagged

0.1.9

Indicators of compromise (SHA-256)

7006e38cfbab1a8bdd4902db6b512d9456dfb9bafd8ba415523a358de81a9bcb

2ee1fb6de5a50d4822e4bbef6900c134a0174abc305eab46305ed777158fb5f1

b67e1d0a9f54f2ca44aa61ecdf60d0caaff8fa29810b95066efc78a5fd4de6d9

3bbd6907e35723bb0b53ea7b799dc1cdad3cd8f45190753c5395f1c14a107610

c9e1324f2687bca43cc3ffa9984bed7948e42d9a29dfe6a0b447c30e1ac65b17

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

Campaign

RLMA-2025-00484GENERIC-standard-pypi-install-pentestRLUA-2026-00498

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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