Malicious Code Injection in wibowo-miemee24-ruro: A Threat to npm Ecosystem

wibowo-miemee24-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110871: Malicious code in wibowo-miemee24-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 Devnack Your last release was probably never penetration tested 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 wibowo-miemee24-ruro is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to the tea.xyz token reward campaign, which has been associated with the proliferation of malicious packages designed to inflate developer reputation scores through automated publishing of derivative packages. The vulnerability stems from the package's design, which allows it to modify critical files and republish itself under various names, thereby compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in wibowo-miemee24-ruro is characterized by the presence of malicious code that alters the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry with derivative packages, which can lead to significant security risks, including unauthorized access and manipulation of user data. The origin of this vulnerability is traced back to the tea.xyz token reward campaign, which exploits the npm ecosystem for malicious purposes.

How To Fix

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

npm uninstall wibowo-miemee24-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 remove the wibowo-miemee24-ruro package from your project by executing the following command: npm uninstall wibowo-miemee24-ruro. This will prevent the malicious code from executing until a fix is applied.

Conclusion

The wibowo-miemee24-ruro package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repopulates the registry with harmful derivatives. It is essential for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for wibowo-miemee24-ruro →

Share this vulnerability

FAQ

wibowo-miemee24-ruro is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your application to security risks and data manipulation.

You should immediately update the package to the latest version or uninstall it to mitigate the risk of exploitation.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall wibowo-miemee24-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