Malicious Code Injection in ripe_pike_z3n: A Threat to npm Ecosystem

ripe_pike_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96377: Malicious code in ripe_pike_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 'ripe_pike_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 linked to the proliferation of malicious packages. These packages often contain scripts that automatically generate and publish derivative packages, compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'ripe_pike_z3n' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the pollution of the npm registry. This behavior not only affects the reputation of developers but also poses a risk to users who may unknowingly install these compromised packages.

How To Fix

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

npm uninstall ripe_pike_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, you can avoid using the 'ripe_pike_z3n' package and monitor your project for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to identify and remove any malicious packages.

Conclusion

The 'ripe_pike_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential harm.

See every vulnerability recorded for ripe_pike_z3n →

Share this vulnerability

FAQ

The 'ripe_pike_z3n' package is an npm package linked to a token reward campaign that has been identified as malicious due to its behavior of publishing derivative packages.

This vulnerability can lead to the installation of malicious packages that may compromise your project's integrity and security, potentially affecting your application's performance and reputation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected by this vulnerability without any signup.

If you have installed 'ripe_pike_z3n', you should uninstall it immediately using 'npm uninstall ripe_pike_z3n' and review your other dependencies for similar vulnerabilities.

There are no patches available for 'ripe_pike_z3n' as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

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