Malicious Code Injection in nurul-dodol60-riris Package: A Threat to npm Users

nurul-dodol60-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88886: Malicious code in nurul-dodol60-riris (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 nurul-dodol60-riris package is part of a broader ecosystem within npm, primarily associated with the tea.xyz token reward campaign. This package, like others in the campaign, is designed to manipulate npm's publishing system by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a target for malicious exploitation.

Vulnerability Detail

The vulnerability in the nurul-dodol60-riris package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to further exploitation or data breaches.

How To Fix

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

npm uninstall nurul-dodol60-riris

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, consider removing the nurul-dodol60-riris package from your project. You can do this by executing the following command: npm uninstall nurul-dodol60-riris. Additionally, monitor your package-lock.json file for any unauthorized changes or additions.

Conclusion

The nurul-dodol60-riris package presents a significant security risk due to its malicious code designed to manipulate npm's publishing system. Developers should take immediate action to remove this package and monitor their projects for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your open-source dependencies.

See every vulnerability recorded for nurul-dodol60-riris →

Share this vulnerability

FAQ

The nurul-dodol60-riris package is part of a campaign that aims to inflate developer reputation scores on npm by automatically generating and publishing numerous derivative packages.

The vulnerability can lead to the installation of malicious packages that compromise your project's integrity and security, potentially exposing sensitive data or allowing unauthorized access.

If you have installed the nurul-dodol60-riris package, it is recommended to uninstall it immediately and check for any unauthorized changes in your project.

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

To prevent future vulnerabilities, regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation.

How To Fix

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

npm uninstall nurul-dodol60-riris

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