Malicious Code Injection in dewi-tapai48-ruro: A Threat to npm Packages

dewi-tapai48-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101494: Malicious code in dewi-tapai48-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 'dewi-tapai48-ruro' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names. This package's primary function is to inflate developer reputation scores for token rewards, but it has been compromised to include malicious scripts that can alter package metadata.

Vulnerability Detail

The vulnerability in 'dewi-tapai48-ruro' originates from its malicious payload, which 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 significant security risks, including the potential for developers to unknowingly use compromised packages, which can further propagate malicious code throughout the ecosystem.

How To Fix

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

npm uninstall dewi-tapai48-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 'dewi-tapai48-ruro' and any packages that depend on it. Additionally, consider using the following command to audit your npm packages for vulnerabilities: npm audit. This will help identify any other potentially vulnerable packages in your project.

Conclusion

The 'dewi-tapai48-ruro' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package and any dependencies associated with it to maintain the integrity of your project. Regular audits and monitoring can help prevent similar vulnerabilities in the future.

See every vulnerability recorded for dewi-tapai48-ruro →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with compromised packages.

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

If you have installed 'dewi-tapai48-ruro', you should remove it immediately and check for any other affected packages in your project.

While specific exploits have not been detailed, the malicious behavior of the package can lead to widespread issues if developers unknowingly use compromised versions.

Regularly audit your dependencies using tools like npm audit and monitor for updates or advisories related to the packages you use.

How To Fix

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

npm uninstall dewi-tapai48-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