Malicious Code Injection in makanabi-aibiuba-uffai: npm Package Vulnerability
Summary
MAL-2025-159251: Malicious code in makanabi-aibiuba-uffai (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 npm package 'makanabi-aibiuba-uffai' is part of a broader campaign involving the tea.xyz token reward system. This package is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. It operates by modifying package metadata and continuously republishing variants, which can lead to pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'makanabi-aibiuba-uffai' stems from its malicious payload that alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall makanabi-aibiuba-uffai
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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using the following command to audit your npm packages for vulnerabilities: 'npm audit'.
Conclusion
The 'makanabi-aibiuba-uffai' npm package contains a serious vulnerability that allows for malicious code injection and registry pollution. It is crucial for developers to remove this package and monitor their dependencies closely. Utilizing tools like Vulert can aid in identifying and managing such vulnerabilities effectively.
See every vulnerability recorded for makanabi-aibiuba-uffai →
FAQ
The primary risk is the potential for malicious code execution and the pollution of the npm registry, which can affect the integrity of other packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Immediately uninstall the package using 'npm uninstall makanabi-aibiuba-uffai' and audit your project for any other vulnerabilities.
Currently, there is no patched version available. It is recommended to remove the package entirely until a safe version is released.
Vulert uses your package-lock.json to monitor for vulnerabilities and provides real-time alerts, helping you maintain the security of your software.