Malicious Code Injection in udin-lapis17-miaww Package - npm Vulnerability

udin-lapis17-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91372: Malicious code in udin-lapis17-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 udin-lapis17-miaww package is part of the npm ecosystem, typically used for JavaScript development. It has been identified as a malicious package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package is particularly dangerous due to its ability to modify critical files and republish itself under various names, thus polluting the npm registry.

Vulnerability Detail

The vulnerability in the udin-lapis17-miaww package originates from its malicious intent to manipulate the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall udin-lapis17-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 workaround, you can avoid using the udin-lapis17-miaww package and any other packages that may have been published by it. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks from malicious packages.

Conclusion

The udin-lapis17-miaww package poses a significant risk due to its malicious behavior of modifying package files and republishing itself. It is crucial for developers to remove this package and monitor their dependencies for any vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for udin-lapis17-miaww →

Share this vulnerability

FAQ

The udin-lapis17-miaww package is a malicious npm package that is part of a campaign to inflate developer reputation scores by generating and republishing derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json file and republishing tainted packages, potentially leading to security issues.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json. Visit Vulert Scanner to check your application without needing to sign up.

If you have installed the udin-lapis17-miaww package, you should uninstall it immediately using npm uninstall udin-lapis17-miaww and check your project for any other affected packages.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your dependencies, ensuring your project remains secure.

How To Fix

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

npm uninstall udin-lapis17-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