Which versions of latentnerf are malicious?

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

How do I remediate latentnerf if I installed it?

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

If latentnerf was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is latentnerf part of a known attack campaign?

Yes — latentnerf is associated with the RLMA-2024-11077, 2024-11-byted-dast, RLUA-2026-00464 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 latentnerf across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for latentnerf (version 9.6).

Part of a larger attack: 2024-11-byted-dast published 183 malicious packages. See the full campaign →

Malicious package

latentnerfPyPI

Advisory published Nov 6, 2024Updated Mar 19, 2026

latentnerf is a confirmed malicious PyPI package (MAL-2024-11623) that steals credentials and exfiltrates sensitive data (malicious version 9.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in latentnerf (PyPI)

MAL-2024-11623

Immediate action

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

pip uninstall latentnerf

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)

d3df574e7fa4fdea4069cd9284140a2e8a2467e37e1d9ee0cd2aa5c503b2e899

8b2d3777f6656f0918d4ae87d53fb8f404fdc59f0f7acb9b733ef2ac2bf1d664

8df122aeab9d653cbe71b02e120e38510e0ffb669ebbc7b64b85f4859ccbc0d7

cc08b6071bdf4dfa31e3dea9393b7b1c6b2c7c933cb5db720712576c4b271a66

05657e625fa8074df1366807eef1decc5ecd13859b1d3a067fa1cb846218bbc7

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for latentnerf (version 9.6).
If you installed it — respond
latentnerf 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 latentnerf was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. latentnerf 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-110772024-11-byted-dastRLUA-2026-00464

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database