Malicious Code Injection in nadia-rangginang46-miaww: A Threat to npm Ecosystem

nadia-rangginang46-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88627: Malicious code in nadia-rangginang46-miaww (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package nadia-rangginang46-miaww 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 generates and publishes derivative packages with randomized names, which can lead to pollution of the npm registry and compromise the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in nadia-rangginang46-miaww originates from its association with a malicious campaign that employs autopublish scripts to manipulate package.json files. This manipulation includes removing private flags, altering version numbers, and creating random package names, which can lead to the proliferation of untrustworthy packages in the npm registry. The ramifications include potential security risks for developers and users who may unknowingly install these compromised packages, leading to further exploitation.

How To Fix

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

npm uninstall nadia-rangginang46-miaww

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 nadia-rangginang46-miaww package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for potential threats.

Conclusion

The nadia-rangginang46-miaww package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.

See every vulnerability recorded for nadia-rangginang46-miaww →

Share this vulnerability

FAQ

nadia-rangginang46-miaww is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the tea.xyz token reward system.

The vulnerability can lead to the installation of untrustworthy packages, potentially compromising your project's security and integrity.

You should immediately remove the nadia-rangginang46-miaww package from your project and monitor for any updates or patches.

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

Yes, 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 nadia-rangginang46-miaww

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