Malicious Code Injection in consistent_scorpion_z3n: npm Package Vulnerability

consistent_scorpion_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93745: Malicious code in consistent_scorpion_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 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

The package 'consistent_scorpion_z3n' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, thereby polluting the npm registry.

Vulnerability Detail

This vulnerability originates from the package's design to include autopublish scripts that manipulate the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to a significant increase in spammy packages in the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall consistent_scorpion_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 avoid using the 'consistent_scorpion_z3n' package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'consistent_scorpion_z3n' package poses a significant risk due to its malicious code that alters package files and floods the npm registry with spam. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for consistent_scorpion_z3n →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json files and publishes spammy variants to the npm registry.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

You should remove the 'consistent_scorpion_z3n' package from your project immediately to mitigate any risks.

Currently, there is no patched version available for 'consistent_scorpion_z3n'. It is advisable to remove the package entirely.

Using this package can lead to security vulnerabilities, including the risk of your project being associated with spammy and malicious packages in the npm registry.

How To Fix

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

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