Which versions of nvidia-clara-sim are malicious?

The following PyPI versions of nvidia-clara-sim are flagged malicious: 0.0.0a0, 999. Treat any of these as compromised.

How do I remediate nvidia-clara-sim if I installed it?

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

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

Yes — nvidia-clara-sim is associated with the GENERIC-standard-pypi-install-pentest 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 nvidia-clara-sim 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 nvidia-clara-sim (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nvidia-clara-sim across your stack and pipelines.

Malicious package

nvidia-clara-simPyPI

Malicious code in nvidia-clara-sim (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10315

Immediate action

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

pip uninstall nvidia-clara-sim

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.

The OpenSSF Package Analysis project identified 'nvidia-clara-sim' @ 999 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

0.0.0a0999

Indicators of compromise (SHA-256)

071cb3befb8e9410c2cdcfa9b987c7ea2628335c45e90dccf0b21b651d6ae71f

0c3253fc14e9a2437aa9a20681b09f89a98de25dad208d585867c157ce1f81b7

c71c25349ac9885da40fc765909e2c5fdcfb90a2ed9424ab5a3f070c74597a35

1a66ac5499a042e2419c44c7d3256e8b7776c2571156dc87e8ae6831fea5f310

291be00c2896afd64c01cf6c5e3648f86cd14f4c9ba5421039f735f9da9dd2a0

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

Campaign

GENERIC-standard-pypi-install-pentest

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks nvidia-clara-sim-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