Malicious Code Injection in makanabi-aibia-ufi: A Threat to npm Packages
Summary
MAL-2025-159240: Malicious code in makanabi-aibia-ufi (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 'makanabi-aibia-ufi' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability in 'makanabi-aibia-ufi' stems from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to reputation inflation for developers. This behavior not only pollutes the npm registry but also poses risks of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall makanabi-aibia-ufiIf 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, consider removing the 'makanabi-aibia-ufi' package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall makanabi-aibia-ufi'. Additionally, monitor your package-lock.json file for any unexpected changes.
Conclusion
The 'makanabi-aibia-ufi' package presents a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their applications.
See every vulnerability recorded for makanabi-aibia-ufi →
FAQ
The primary risk is the potential for malicious code execution and the pollution of the npm registry, which can lead to security vulnerabilities in applications that depend on this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground at Vulert Scanner, you can check your application without any signup.
If an immediate update is not possible, consider removing the package and monitoring your application for any unusual behavior. Implementing strict dependency management practices can also help mitigate risks.
While specific exploits have not been publicly disclosed, the nature of the malicious code suggests that it could be leveraged for dependency confusion attacks or to introduce further vulnerabilities into applications.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about security advisories related to the packages you use.
