Malicious Code Injection in mulyono-mieaceh11-miaww Package

mulyono-mieaceh11-miaww Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88506: Malicious code in mulyono-mieaceh11-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The mulyono-mieaceh11-miaww package is part of the npm ecosystem, often used for various JavaScript applications. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish numerous variants with randomized names.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the mulyono-mieaceh11-miaww package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The implications of this vulnerability include potential security risks for developers who unknowingly use these compromised packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall mulyono-mieaceh11-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 workaround, you can avoid using the mulyono-mieaceh11-miaww package altogether. If it is already part of your project, consider removing it and replacing it with a trusted alternative. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The mulyono-mieaceh11-miaww package poses a significant security risk due to its malicious code that modifies package configurations and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for mulyono-mieaceh11-miaww →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

Using the compromised package can lead to security risks, including the potential exposure of sensitive data and the pollution of your project's dependency tree.

You should remove the mulyono-mieaceh11-miaww package from your project and monitor for any updates or patches that may be released.

You can use tools like Vulert, which allows you to monitor and receive alerts for open-source vulnerabilities in your software without requiring code access.

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 mulyono-mieaceh11-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