Malicious Code Injection in solid_jaguar_z3n: A Threat to npm Packages

solid_jaguar_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108912: Malicious code in solid_jaguar_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package solid_jaguar_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in solid_jaguar_z3n stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to publish derivative packages automatically, which can lead to pollution of the npm registry and potential security risks for users who unknowingly install these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's package management system.

How To Fix

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

npm uninstall solid_jaguar_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 solid_jaguar_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The solid_jaguar_z3n package poses a significant risk due to its malicious code that alters package metadata and publishes compromised versions. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for solid_jaguar_z3n →

Share this vulnerability

FAQ

solid_jaguar_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating package metadata and inflating developer reputation scores.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks, including unauthorized access to your application or data.

You should uninstall the package immediately using the command npm uninstall solid_jaguar_z3n and check for any dependencies that may rely on it.

Regularly audit your dependencies using tools like Vulert, which can monitor and alert you to open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

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