Malicious Code Injection in maka-anima-gugag: A Threat to npm Users
Summary
MAL-2025-159148: Malicious code in maka-anima-gugag (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 'maka-anima-gugag' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. This package is particularly concerning due to its ability to modify critical files and continuously republish variants, leading to potential pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'maka-anima-gugag' originates from its malicious payload, which modifies the package.json file by removing private flags and changing version numbers. It generates random Indonesian-themed package names and continuously republishes these variants. This behavior can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and potentially compromising the integrity of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maka-anima-gugagIf 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 remove the 'maka-anima-gugag' package from your project by executing: npm uninstall maka-anima-gugag. Additionally, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The 'maka-anima-gugag' package poses a significant threat due to its malicious code that alters package files and repopulates the npm registry with potentially harmful variants. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing monitoring.
See every vulnerability recorded for maka-anima-gugag →
FAQ
The main issue is that it contains malicious code that modifies package.json files and republish variants, leading to npm registry pollution.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you cannot update the package, it is advisable to remove it from your project to prevent any potential security risks.
Using compromised packages can lead to security vulnerabilities, data breaches, and the potential for malicious actors to exploit your application.
Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time, alerting you to any issues.
