Malicious Code Injection in wati-oncom50-ruro Package

wati-oncom50-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110704: Malicious code in wati-oncom50-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The wati-oncom50-ruro package is part of the npm ecosystem, commonly used for various JavaScript applications. It is designed to facilitate certain functionalities within these applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful packages, which can compromise the integrity and security of applications that depend on it.

Vulnerability Detail

The vulnerability stems from the wati-oncom50-ruro package being associated with the tea.xyz token reward campaign, which utilizes autopublish scripts to generate and publish derivative packages with randomized names. This malicious behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access, and degradation of the npm ecosystem.

How To Fix

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

npm uninstall wati-oncom50-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 wati-oncom50-ruro package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert to stay informed about vulnerabilities.

Conclusion

The wati-oncom50-ruro package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for wati-oncom50-ruro →

Share this vulnerability

FAQ

The wati-oncom50-ruro package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of harmful derivative packages.

This vulnerability can lead to unauthorized modifications in your application's dependencies, potentially exposing sensitive data and compromising application integrity.

You should uninstall the wati-oncom50-ruro package immediately and monitor your application for any unusual behavior. Consider using alternative packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall wati-oncom50-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