Malicious Code Injection in wawan-kacang75-ruro Package

wawan-kacang75-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110735: Malicious code in wawan-kacang75-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 wawan-kacang75-ruro package is part of the npm ecosystem and appears to be involved in a token reward campaign associated with tea.xyz. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's design to automatically modify its own package.json file, removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to the proliferation of malicious packages, potentially affecting developers and users who rely on the npm ecosystem for secure package management.

How To Fix

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

npm uninstall wawan-kacang75-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 manually remove the package from your project by running the command: npm uninstall wawan-kacang75-ruro. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The wawan-kacang75-ruro package has been identified as containing malicious code that poses a significant risk to users and developers within the npm ecosystem. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security.

See every vulnerability recorded for wawan-kacang75-ruro →

Share this vulnerability

FAQ

It is an npm package involved in a token reward campaign that generates and publishes derivative packages.

The vulnerability can lead to the proliferation of malicious packages, compromising the security and integrity of your project.

You should uninstall the package immediately and monitor your project for any further vulnerabilities.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

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