Malicious Code Injection in danangwijaya Package: npm Vulnerability Overview

danangwijaya Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171075: Malicious code in danangwijaya (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 danangwijaya package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability in the danangwijaya package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages in their projects. The malicious scripts (auto.js, autopublish.js, etc.) are designed to continuously republish variants, further exacerbating the issue.

How To Fix

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

npm uninstall danangwijaya

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, avoid using the danangwijaya package and consider replacing it with a reputable alternative. Regularly audit your package dependencies to ensure they are secure.

Conclusion

The danangwijaya package poses a significant security risk due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant in monitoring their dependencies and to take immediate action to remove any compromised packages. Utilizing tools like Vulert can help in maintaining the security of your projects.

See every vulnerability recorded for danangwijaya →

Share this vulnerability

FAQ

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

Using the danangwijaya package can lead to security risks, including the potential for your project to be polluted with malicious code and compromised packages.

You should uninstall the danangwijaya package immediately using the command 'npm uninstall danangwijaya' and audit your project for any other potentially malicious 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 check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies, use trusted packages, and stay informed about known vulnerabilities in the npm ecosystem to minimize risks.

How To Fix

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

npm uninstall danangwijaya

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