Malicious Code Injection in slippery_chinchilla_z3n Package

slippery_chinchilla_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108837: Malicious code in slippery_chinchilla_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The slippery_chinchilla_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 scripts that compromise its integrity and the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the slippery_chinchilla_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall slippery_chinchilla_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 measure, avoid using the slippery_chinchilla_z3n package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The slippery_chinchilla_z3n package poses a significant risk due to its malicious code that alters package metadata and can compromise the npm registry. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for slippery_chinchilla_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json, removes private flags, and can lead to the pollution of the npm registry, affecting your project's integrity.

You should remove the slippery_chinchilla_z3n package from your project and monitor for any updates or patches.

You can use Vulert, which analyzes your package-lock.json file to provide real-time alerts for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring an account.

How To Fix

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

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