Malicious Code Injection in dewanto-tapai3-ruro: A Threat to npm Ecosystem

dewanto-tapai3-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101448: Malicious code in dewanto-tapai3-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 dewanto-tapai3-ruro is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in dewanto-tapai3-ruro stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising other packages. The origin of this vulnerability is linked to a broader campaign that exploits npm's publishing mechanisms for malicious purposes.

How To Fix

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

npm uninstall dewanto-tapai3-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 dewanto-tapai3-ruro package from your project by executing the following command: 'npm uninstall dewanto-tapai3-ruro'. This will prevent any malicious activity associated with the package until a fix is applied.

Conclusion

The dewanto-tapai3-ruro package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be aware of such vulnerabilities and take appropriate actions to secure their projects. Regularly updating packages and using tools like Vulert can help in maintaining the integrity of your software.

See every vulnerability recorded for dewanto-tapai3-ruro →

Share this vulnerability

FAQ

Dewanto-tapai3-ruro is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

If you cannot update the package, consider removing it from your project as a temporary measure until a fix is available.

More information can be found in the vulnerability report on the GitHub repository for malicious packages.

How To Fix

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

npm uninstall dewanto-tapai3-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