Malicious Code Exploit in dodynugroho Package: npm Vulnerability Overview

dodynugroho Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171116: Malicious code in dodynugroho (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 dodynugroho package is part of the npm ecosystem, often utilized for various JavaScript applications. However, it has been identified as part of a malicious campaign linked to the tea.xyz token reward initiative. This campaign has led to the proliferation of numerous packages designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The dodynugroho package contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is intended to continuously republish variants of the package, polluting the npm registry and potentially compromising the integrity of applications that depend on it. The vulnerability originates from a broader malicious strategy aimed at exploiting npm's package management system.

How To Fix

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

npm uninstall dodynugroho

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 dodynugroho package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The dodynugroho package poses a significant risk due to its malicious code designed to manipulate npm's package management system. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.

See every vulnerability recorded for dodynugroho →

Share this vulnerability

FAQ

The dodynugroho package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of applications that rely on the dodynugroho package, potentially introducing security risks.

You should uninstall the dodynugroho package immediately using 'npm uninstall dodynugroho' and check for any other affected packages.

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues.

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

How To Fix

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

npm uninstall dodynugroho

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