Malicious Code Injection in dono-sasag53-ruro Package

dono-sasag53-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101726: Malicious code in dono-sasag53-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 dono-sasag53-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards but has been compromised to include malicious scripts that manipulate package metadata. The vulnerability arises from the package's ability to modify its own package.json file, which can lead to severe consequences for developers relying on its integrity.

Vulnerability Detail

The vulnerability in the dono-sasag53-ruro package is characterized by the presence of malicious code that alters the package.json file to remove private flags, change version numbers, and generate random package names. This behavior is intended to inflate developer reputation scores through the automatic generation and publication of derivative packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood the npm registry with such malicious packages. The ramifications include potential pollution of the npm registry, loss of trust in the package ecosystem, and unintended consequences for developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall dono-sasag53-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 the dono-sasag53-ruro package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The dono-sasag53-ruro package has been identified as containing malicious code that compromises its integrity and poses risks to developers. It is crucial to take immediate action by uninstalling the package and monitoring for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for dono-sasag53-ruro →

Share this vulnerability

FAQ

The dono-sasag53-ruro package is an npm package associated with the tea.xyz token reward campaign, designed to facilitate token distribution.

The malicious code can modify your package.json file, leading to unauthorized changes and potential pollution of the npm registry.

You should uninstall the dono-sasag53-ruro package immediately and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

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

How To Fix

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

npm uninstall dono-sasag53-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