Malicious Code Injection in hadi-wajit48-ruro Package: npm Vulnerability Overview

hadi-wajit48-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103477: Malicious code in hadi-wajit48-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 hadi-wajit48-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's primary functionality is to facilitate the distribution of JavaScript libraries, but it has been compromised to serve malicious purposes.

Vulnerability Detail

The vulnerability in the hadi-wajit48-ruro package stems from its inclusion in a campaign that deploys autopublish scripts designed to generate and publish derivative packages with randomized names. These scripts modify the package.json file by removing private flags, altering version numbers, and continuously republishing variants to clutter the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to 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 hadi-wajit48-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 measure, you can avoid using the hadi-wajit48-ruro package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.

Conclusion

The hadi-wajit48-ruro package poses a significant risk due to its malicious code injection aimed at manipulating the npm ecosystem. It is crucial for developers to be vigilant, remove compromised packages, and utilize tools like Vulert to monitor their dependencies for vulnerabilities.

See every vulnerability recorded for hadi-wajit48-ruro →

Share this vulnerability

FAQ

The hadi-wajit48-ruro package is an npm package that has been compromised as part of a malicious campaign to inflate developer reputation scores.

This vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

You should immediately remove the hadi-wajit48-ruro package from your project and check for any other affected packages.

You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert can monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

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 hadi-wajit48-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