Which versions of instructnerf2nerf are malicious?

The following PyPI versions of instructnerf2nerf are flagged malicious: 9.6. Treat any of these as compromised.

How do I remediate instructnerf2nerf if I installed it?

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

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

Yes — instructnerf2nerf is associated with the RLMA-2024-11069, 2024-11-byted-dast, RLUA-2026-00428 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 instructnerf2nerf 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 instructnerf2nerf (version 9.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging instructnerf2nerf across your stack and pipelines.

Malicious package

instructnerf2nerfPyPI

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

MAL-2024-11616

Immediate action

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

pip uninstall instructnerf2nerf

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

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: 2024-11-byted-dast

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.
typosquatting
dependency-confusion

Malicious versions

1 flagged

9.6

Indicators of compromise (SHA-256)

0859d3899fa660c7aabdeb7a3c13691ea4029055d29b16f00010cf4d546a1d9c

b0da4dbc83454b9463f22324c13c3f0077e14280550b34488993bc7bb193ce86

4f8dc79e61b48a344ec9117b2a5c0ccc5c262b2b14b42d100584ac667ad7cdcf

2c9d94bcfe116f7e6a0ba4a18c775d570c023e738ed4923132acba74850838b4

a92758effab0c1ba8d94b5a305cc9c16a20016267f89c7d90e1f39cc8f388786

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

Campaign

RLMA-2024-110692024-11-byted-dastRLUA-2026-00428

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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