Malicious Code Injection in verify-aikn-misualaibaku Package
Summary
MAL-2025-170266: Malicious code in verify-aikn-misualaibaku (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 verify-aikn-misualaibaku 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 inflate developer reputation scores through the creation of numerous derivative packages. Its functionality is compromised by the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the package being part of a broader malicious campaign associated with the tea.xyz token reward initiative. The malicious code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall verify-aikn-misualaibakuIf 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 measure, avoid using the verify-aikn-misualaibaku package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies to identify any potential vulnerabilities.
Conclusion
The verify-aikn-misualaibaku package has been compromised by malicious code that alters its functionality and poses significant risks to developers. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.
See every vulnerability recorded for verify-aikn-misualaibaku →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should immediately uninstall the package and monitor your application for any unusual behavior. Consider using alternative packages.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
