Malicious Code Injection in wati-tahu38-ruro Package: npm Vulnerability

wati-tahu38-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110718: Malicious code in wati-tahu38-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The wati-tahu38-ruro package is part of a series of npm packages that emerged during 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. The functionality of this package is compromised due to the presence of malicious scripts that manipulate its metadata.

Vulnerability Detail

The vulnerability in the wati-tahu38-ruro package stems from malicious code that modifies the package.json file to remove private flags and alters version numbers. This code generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The origin of this vulnerability is linked to a broader campaign aimed at exploiting the npm ecosystem for token rewards, potentially leading to reputational damage for developers and security risks for users.

How To Fix

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

npm uninstall wati-tahu38-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 prevent the malicious scripts from executing by removing the package from your project. Use the following command to uninstall it: npm uninstall wati-tahu38-ruro.

Conclusion

The wati-tahu38-ruro package contains malicious code that poses significant risks to developers and users alike. It is essential to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the integrity of your software.

See every vulnerability recorded for wati-tahu38-ruro →

Share this vulnerability

FAQ

The wati-tahu38-ruro package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted or malicious packages.

If you have installed the wati-tahu38-ruro package, it is crucial to uninstall it immediately to mitigate any potential risks.

Yes, 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.

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 wati-tahu38-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