Malicious Code Injection in tadashi-tu-rwew Package: npm Vulnerability

tadashi-tu-rwew Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-166688: Malicious code in tadashi-tu-rwew (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 tadashi-tu-rwew package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the tadashi-tu-rwew package originates from its involvement in a token reward campaign that utilizes autopublish scripts. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. This malicious behavior can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.

How To Fix

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

npm uninstall tadashi-tu-rwew

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 tadashi-tu-rwew package from your project by executing the following command: npm uninstall tadashi-tu-rwew. This will prevent any potential malicious activity associated with this package until a fix is applied.

Conclusion

The tadashi-tu-rwew package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to be aware of this vulnerability and take appropriate action to protect their projects. Regularly updating packages and utilizing monitoring tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for tadashi-tu-rwew →

Share this vulnerability

FAQ

The tadashi-tu-rwew package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

This vulnerability can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of your project and affecting dependencies.

If you are using the tadashi-tu-rwew package, it is advisable to uninstall it and monitor for any updates or patches from the maintainers.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall tadashi-tu-rwew

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