Malicious Code Injection in masako-m-gunung: A Threat to npm Ecosystem
Summary
MAL-2025-160148: Malicious code in masako-m-gunung (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'masako-m-gunung' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and the integrity of the registry itself.
Vulnerability Detail
The vulnerability in 'masako-m-gunung' originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts designed to automatically publish derivative packages with randomized names. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall masako-m-gunungIf 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 'masako-m-gunung' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can analyze your package-lock.json file for potential threats.
Conclusion
The 'masako-m-gunung' package poses a significant threat to the npm ecosystem due to its malicious intent to manipulate the registry and developer reputations. It is crucial for developers to be vigilant and remove such packages from their projects while utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for masako-m-gunung →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
Using this package can compromise your project's integrity and reputation, as it may lead to the inclusion of malicious code.
You should remove the package from your project and monitor for any updates or patches that may address the vulnerability.
You can use Vulert, which analyzes your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
