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

ade-brongkos62-ruro Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99135: Malicious code in ade-brongkos62-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'ade-brongkos62-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 inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in 'ade-brongkos62-ruro' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, polluting the npm registry and potentially leading to security risks for users who install these packages. The malicious code can compromise the integrity of applications relying on this package, making it a serious concern for developers.

How To Fix

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

npm uninstall ade-brongkos62-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 workaround, you can avoid using 'ade-brongkos62-ruro' and any other packages associated with the tea.xyz token reward campaign. Instead, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The 'ade-brongkos62-ruro' package poses a significant threat due to its malicious code designed to manipulate npm registry entries. It is essential for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for ade-brongkos62-ruro →

Share this vulnerability

FAQ

The primary risk is the injection of malicious code that can compromise your application's integrity and security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

You should immediately remove the 'ade-brongkos62-ruro' package from your project and monitor for any updates or patches.

Yes, consider using other reputable npm packages that offer similar functionality without the associated risks.

Vulert uses your package-lock.json to monitor and alert you in real-time for any open-source vulnerabilities, helping you maintain a secure application.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall ade-brongkos62-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