Malicious Code Injection in bashirakrambashirakram Package
Summary
MAL-2025-170954: Malicious code in bashirakrambashirakram (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 bashirakrambashirakram package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, this package has been found to contain malicious scripts that compromise its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the bashirakrambashirakram package originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bashirakrambashirakramIf 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 bashirakrambashirakram package from your project by executing the command: npm uninstall bashirakrambashirakram. This will prevent any malicious scripts from executing until a fix is applied.
Conclusion
The bashirakrambashirakram package contains a significant vulnerability that can compromise the integrity of the npm registry and the security of applications using it. It is crucial for developers to take immediate action by updating or removing the package to protect their projects.
See every vulnerability recorded for bashirakrambashirakram →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and exposing your project to potential security risks.
You should update the package to a patched version or remove it from your project to mitigate the risks associated with this vulnerability.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can also check your application for vulnerabilities using the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
