Which versions of nerfstudio-gs are malicious?

The following PyPI versions of nerfstudio-gs are flagged malicious: 99.0.0, 99.0.1, 99.0.2, 99.0.3. Treat any of these as compromised.

How do I remediate nerfstudio-gs if I installed it?

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

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

Yes — nerfstudio-gs is associated with the 2026-06-nerfstudio-gs 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 nerfstudio-gs 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 nerfstudio-gs (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nerfstudio-gs across your stack and pipelines.

Malicious package

nerfstudio-gsPyPI

Malicious code in nerfstudio-gs (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5333

Immediate action

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

pip uninstall nerfstudio-gs

What this malware does

During installation or Python setup (via PTH file), the code exfiltrated all kinds of sensitive data, including env variables, browser's data, SSH keys, data from cryptocurrency extensions, shell history files, etc.

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

Campaign: 2026-06-nerfstudio-gs

Reasons (based on the campaign):

dependency-confusion
exfiltration-credentials
exfiltration-browser-data
exfiltration-crypto
exfiltration-env-variables
files-exfiltration
exfiltration-ssh-keys
The package overrides the install command in setup.py to execute malicious code during installation.
abuses-pth

Malicious versions

4 flagged

99.0.099.0.199.0.299.0.3

Indicators of compromise (SHA-256)

523b928ceb73227e96f02eb85783222da17d0e716c9c7012b4cbcafd1e787f58

42534f036c9f6bfba22f4712a4c2bd08fd66656db742bb2ce60daaad0d38fcca

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

Campaign

2026-06-nerfstudio-gs

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks nerfstudio-gs-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