Which versions of libspatialindex are malicious?

The following PyPI versions of libspatialindex are flagged malicious: 10.0.2, 11.0.2. Treat any of these as compromised.

How do I remediate libspatialindex if I installed it?

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

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

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

Malicious package

libspatialindexPyPI

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

MAL-2025-6536

Immediate action

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

pip uninstall libspatialindex

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.

Malicious versions

2 flagged

10.0.211.0.2

Indicators of compromise (SHA-256)

40ada2258e536b3404a1e4315403540c2a3c1cb925db29168ef72badfffb8e2c

a8f84b78d11dd4ee52e30df4d4f25da3122b7cdc8a5cad5bee4e7e3b42e49b43

6b0bc61dcf57d6bcb1a6bd12a1d9d143a3bc46139a6cf4544e2c23f50f361b50

ac9157a60c6755765832eb5ed801725c24e0b3d5f192ca15cff68e1fca23ead9

4bb5003aa4dc8035e73697b29278c24a9e3a13cb0748737b12eea81ab4bbf8d1

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

Campaign

RLMA-2025-03630GENERIC-standard-pypi-install-pentestRLUA-2026-00472

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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