Which versions of nirohf-reverse-shell are malicious?

The following PyPI versions of nirohf-reverse-shell are flagged malicious: 0.6, 2.6. Treat any of these as compromised.

How do I remediate nirohf-reverse-shell if I installed it?

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

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

Yes — nirohf-reverse-shell is associated with the 2023-12-09-nirohf-reverse-shell 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 nirohf-reverse-shell 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 nirohf-reverse-shell (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nirohf-reverse-shell across your stack and pipelines.

Malicious package

nirohf-reverse-shellPyPI

Malicious code in nirohf-reverse-shell (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12314

Immediate action

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

pip uninstall nirohf-reverse-shell

What this malware does

Installing starts a reverse shell

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

Campaign: 2023-12-09-nirohf-reverse-shell

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

2 flagged

0.62.6

Indicators of compromise (SHA-256)

0a9d6f7f525a7507406f078525c8094a0aaba6d2b5c723d7b74f6c895f16c310

c2b0a9ce248bca096b5109a73b943559cabbd6f77433d4a64cd1c804f7ec88df

1cf197043de97161435f1b7b122aeb5b744c5573f495a7eacf77a3a1aa72d787

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

Campaign

2023-12-09-nirohf-reverse-shell

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks nirohf-reverse-shell-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