Malicious Code Injection in spatial_python_z3n Package - npm Vulnerability

spatial_python_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96699: Malicious code in spatial_python_z3n (npm). Affected versions are not published. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The spatial_python_z3n package is part of the npm ecosystem, primarily used for various spatial data manipulations and analyses. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users relying on this package.

Vulnerability Detail

The vulnerability in the spatial_python_z3n package originates from its association with the tea.xyz token reward campaign. This malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants clutters the npm registry, making it difficult for developers to identify legitimate packages. The ramifications include potential exposure to untrusted code, which can lead to security breaches and loss of data integrity.

How To Fix

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

npm uninstall spatial_python_z3n

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 workaround, you can remove the spatial_python_z3n package from your project until a secure version is released. Use the following command to uninstall it: npm uninstall spatial_python_z3n. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The spatial_python_z3n package has been identified as vulnerable due to its involvement in a malicious npm campaign. Users are advised to update or remove the package to mitigate risks associated with this vulnerability. Regular monitoring and auditing of dependencies are crucial for maintaining application security.

See every vulnerability recorded for spatial_python_z3n →

Share this vulnerability

FAQ

The spatial_python_z3n package is utilized for spatial data manipulations and analyses within the npm ecosystem.

You can check if your application is affected by this vulnerability using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to analyze your package-lock.json.

Using a compromised package can expose your application to malicious code, leading to data breaches, unauthorized access, and potential loss of user trust.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

If immediate updates are not possible, consider removing the package and looking for alternative solutions until a secure version is available.

How To Fix

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

npm uninstall spatial_python_z3n

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