Malicious Code Injection in spatial_pelican_z3n Package

spatial_pelican_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108981: Malicious code in spatial_pelican_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The spatial_pelican_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity.

Vulnerability Detail

The vulnerability stems from the presence of malicious scripts within the spatial_pelican_z3n package. These scripts, such as auto.js and autopublish.js, are designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers' reputations and project integrity.

How To Fix

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

npm uninstall spatial_pelican_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 manually remove the spatial_pelican_z3n package from your project by running the command: npm uninstall spatial_pelican_z3n. Additionally, consider monitoring your package-lock.json file for any unauthorized changes.

Conclusion

The spatial_pelican_z3n package contains malicious code that poses a significant risk to developers and their projects. Immediate action is required to remove the package and monitor for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for spatial_pelican_z3n →

Share this vulnerability

FAQ

The spatial_pelican_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to reputation damage and project instability.

If you have installed the spatial_pelican_z3n package, it is crucial to uninstall it immediately and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.

To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall spatial_pelican_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