Malicious Code Injection in wawan-rangginang55-ruro: A Threat to npm Ecosystem

wawan-rangginang55-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110751: Malicious code in wawan-rangginang55-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 wawan-rangginang55-ruro is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to developers and users alike.

Vulnerability Detail

The vulnerability in wawan-rangginang55-ruro stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to the proliferation of untrustworthy packages, potentially compromising the integrity of applications that depend on them.

How To Fix

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

npm uninstall wawan-rangginang55-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 workaround, you can monitor your project for vulnerabilities using tools like Vulert. By utilizing the Vulert playground at https://vulert.com/scanner, you can check if your application is affected by this vulnerability without requiring any signup. This tool analyzes your package-lock.json file to provide real-time alerts for open-source vulnerabilities.

Conclusion

The wawan-rangginang55-ruro package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is essential to take immediate action by removing the package and monitoring your dependencies to ensure the security of your applications. Utilizing tools like Vulert can aid in identifying and addressing vulnerabilities effectively.

See every vulnerability recorded for wawan-rangginang55-ruro →

Share this vulnerability

FAQ

wawan-rangginang55-ruro is an npm package that is part of a malicious campaign aimed at manipulating package metadata and inflating developer reputation scores.

The vulnerability can lead to the inclusion of untrustworthy packages in your application, potentially compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall wawan-rangginang55-ruro' and monitor your dependencies for any further vulnerabilities.

Regularly update your dependencies, use trusted packages, and utilize tools like Vulert to monitor for vulnerabilities in your project.

Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities by analyzing your package-lock.json file.

How To Fix

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

npm uninstall wawan-rangginang55-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