Which versions of nspacercesolve are malicious?

The following PyPI versions of nspacercesolve are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7. Treat any of these as compromised.

How do I remediate nspacercesolve if I installed it?

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

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

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

Malicious package

nspacercesolvePyPI

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

MAL-2025-191805

Immediate action

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

pip uninstall nspacercesolve

What this malware does

During installation, the package looks for a flag file and exfiltrates it. Similar content is in the main file. 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: 2025-11-nspacercesolve

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.
other
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

7 flagged

0.0.10.0.20.0.30.0.40.0.50.0.60.0.7

Indicators of compromise (SHA-256)

f2fd9d525b9b0d37c2d5dbce66a43d1b111066d3c087f3f000474640e192cf54

8a8c6f18d1f22d3d0f0b9902a176d91fdfe33270faea47c835a0078955b85914

2379596f36f8f2fa75b80435f350d857ce43541342e77668e9532b0c8538c6fe

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

Campaign

2025-11-nspacercesolve

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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