Malicious Code Injection in dian-getuk49-ruro: A Threat to npm Ecosystem

dian-getuk49-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101513: Malicious code in dian-getuk49-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 package dian-getuk49-ruro is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from the malicious design of the dian-getuk49-ruro package, which includes scripts that automatically modify package.json files. These modifications remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also compromises the security and reliability of dependent applications. The malicious payload can potentially allow unauthorized access to sensitive information and disrupt normal package management operations.

How To Fix

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

npm uninstall dian-getuk49-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 dian-getuk49-ruro package and any other packages associated with the tea.xyz campaign. Monitor your package-lock.json file for any unauthorized changes and revert them if necessary.

Conclusion

The dian-getuk49-ruro package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to remove this package and monitor their dependencies for security vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your applications.

See every vulnerability recorded for dian-getuk49-ruro →

Share this vulnerability

FAQ

dian-getuk49-ruro is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your application to security risks and instability.

You should immediately uninstall the dian-getuk49-ruro package using 'npm uninstall dian-getuk49-ruro' and review your dependencies for any other malicious packages.

You can use Vulert to monitor your application for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert alerts you to any potential threats.

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 dian-getuk49-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