Malicious Code Vulnerability in libspatialindex: A Critical Security Concern

libspatialindex Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6536: Malicious code in libspatialindex (PyPI). Affects libspatialindex versions 11.0.2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libspatialindex is a Python package that provides a spatial indexing library, allowing efficient spatial data management and querying. It is widely used in applications that require spatial data structures, such as geographic information systems (GIS) and spatial databases. However, a recent vulnerability has been identified that exposes users to potential malicious code execution.

Vulnerability Detail

The vulnerability identified as MAL-2025-6536 in the libspatialindex package is due to the presence of malicious code within version 11.0.2. This code can lead to unauthorized access and manipulation of user data, posing significant risks to application integrity and user security. The malicious code was discovered by ReversingLabs, highlighting the importance of vigilance in package management and the potential consequences of using compromised libraries.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall libspatialindex

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, users may consider removing the affected version of the libspatialindex package until a secure version is confirmed. This can be done using the command: pip uninstall libspatialindex. However, this may affect any applications relying on this package.

Conclusion

The discovery of malicious code in the libspatialindex package underscores the importance of maintaining secure software dependencies. Users are urged to update to the latest version to protect their applications from potential threats. Utilizing tools like Vulert can further enhance security by providing real-time vulnerability monitoring.

See every vulnerability recorded for libspatialindex →

Share this vulnerability

FAQ

The vulnerability involves malicious code embedded in version 11.0.2 of the libspatialindex package, which can lead to unauthorized access and data manipulation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If an immediate update is not possible, consider uninstalling the affected version to mitigate risks until a secure version is available.

The vulnerability was discovered by ReversingLabs, a cybersecurity firm specializing in threat detection and analysis.

While specific exploits have not been publicly disclosed, the presence of malicious code indicates a high risk of exploitation, making it crucial to address the vulnerability promptly.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall libspatialindex

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback