Malicious Code Injection in ade-jengkol2-ruro: A Threat to npm Ecosystem

ade-jengkol2-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99140: Malicious code in ade-jengkol2-ruro (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 package 'ade-jengkol2-ruro' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The malicious nature of this package poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in 'ade-jengkol2-ruro' originates from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks, dependency confusion, and a compromised development environment. The malicious payload can affect any project that inadvertently includes this package, leading to unintended consequences.

How To Fix

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

npm uninstall ade-jengkol2-ruro

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 'ade-jengkol2-ruro' package and any packages that may depend on it. Review your package-lock.json file to identify any dependencies that might include this malicious package.

Conclusion

The 'ade-jengkol2-ruro' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remove this package and monitor their dependencies regularly to maintain a secure development environment. Utilizing tools like Vulert can help in identifying and addressing vulnerabilities effectively.

See every vulnerability recorded for ade-jengkol2-ruro →

Share this vulnerability

FAQ

The 'ade-jengkol2-ruro' package is part of a malicious npm package campaign that aims to manipulate the npm registry.

You can check your package-lock.json file for the presence of 'ade-jengkol2-ruro'. Additionally, you can use Vulert's playground to monitor for vulnerabilities.

Using this package can lead to security vulnerabilities, dependency confusion, and potential exploitation of your development environment.

There is no patch for 'ade-jengkol2-ruro' as it is recommended to remove the package entirely from your project.

Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights without requiring code access.

How To Fix

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

npm uninstall ade-jengkol2-ruro

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