Malicious Code Injection in indah-dodol40-ruro Package

indah-dodol40-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104098: Malicious code in indah-dodol40-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 indah-dodol40-ruro package is part of the npm ecosystem, often used for various JavaScript applications. This package has been identified as part of a malicious campaign that exploits npm's publishing capabilities. Its primary function is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the indah-dodol40-ruro package stems from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to security breaches and loss of reputation.

How To Fix

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

npm uninstall indah-dodol40-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 indah-dodol40-ruro package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before including them in your project.

Conclusion

The indah-dodol40-ruro package poses a significant risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages from their projects.

See every vulnerability recorded for indah-dodol40-ruro →

Share this vulnerability

FAQ

The indah-dodol40-ruro package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

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

If you have installed the indah-dodol40-ruro package, you should uninstall it immediately and review your project's dependencies for any other potentially compromised packages.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against known vulnerabilities using the Vulert playground.

To prevent future vulnerabilities, always verify the source and integrity of packages before installation, keep your dependencies updated, and utilize monitoring tools like Vulert.

How To Fix

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

npm uninstall indah-dodol40-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