Malicious Code Injection in lutfi-dodol16-ruro: A Threat to npm Ecosystem

lutfi-dodol16-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105393: Malicious code in lutfi-dodol16-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package lutfi-dodol16-ruro 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 known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous derivative packages, thereby inflating developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in lutfi-dodol16-ruro arises from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of variants. This behavior not only pollutes the npm registry but can also compromise the integrity of applications relying on these packages. The origin of this issue is linked to the broader campaign aimed at exploiting npm for token rewards, making it a significant concern for developers and users alike.

How To Fix

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

npm uninstall lutfi-dodol16-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 workaround, you can temporarily avoid using the lutfi-dodol16-ruro package by removing it from your dependencies. You can do this by executing the following command: npm uninstall lutfi-dodol16-ruro. Additionally, consider using alternative packages that do not exhibit malicious behavior.

Conclusion

The lutfi-dodol16-ruro package poses a significant risk due to its malicious behavior, which can compromise the npm ecosystem. It is essential for developers to remain vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for lutfi-dodol16-ruro →

Share this vulnerability

FAQ

lutfi-dodol16-ruro is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry for token rewards.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.

If you have installed lutfi-dodol16-ruro, you should uninstall it immediately and monitor your application for any unusual behavior.

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

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

How To Fix

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

npm uninstall lutfi-dodol16-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