Malicious Code Injection in mahnud-nofty-gogia Package
Summary
MAL-2025-159091: Malicious code in mahnud-nofty-gogia (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 mahnud-nofty-gogia 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 that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to reputation inflation for the tea protocol token rewards. The package modifies critical files, such as package.json, to remove private flags and alter version numbers, thereby posing a significant risk to developers and their projects.
Vulnerability Detail
The vulnerability in the mahnud-nofty-gogia package originates from its involvement in a token reward campaign that floods the npm registry with malicious packages. The malicious payload alters the package.json file, removing private flags and changing version numbers. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include loss of control over package versions, exposure to further malicious code, and damage to developer reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mahnud-nofty-gogiaIf 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 prevent the installation of the mahnud-nofty-gogia package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include this package by regularly auditing your dependencies with 'npm audit'. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The mahnud-nofty-gogia package poses a significant risk due to its malicious behavior, which can compromise the integrity of your project. It is crucial to take immediate action by removing the package and monitoring your dependencies for vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your open-source software.
See every vulnerability recorded for mahnud-nofty-gogia →
FAQ
The mahnud-nofty-gogia package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially allowing malicious code to be executed in your project.
You should uninstall the mahnud-nofty-gogia package immediately and audit your project for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
