Malicious Code Injection in hassanameen Package: npm Vulnerability Overview
Summary
MAL-2025-171299: Malicious code in hassanameen (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 hassanameen package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages that can compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the hassanameen package stems from its malicious code that alters the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the reputation of legitimate developers but also poses a risk of dependency confusion and potential exploitation of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall hassanameen
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, consider removing the hassanameen package from your project if it is not essential. You can do this by executing the command: 'npm uninstall hassanameen'. Additionally, you may want to monitor your package-lock.json file for any unauthorized changes.
Conclusion
The hassanameen package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. It is essential to take immediate action by updating or removing the package and monitoring your dependencies for any vulnerabilities.
See every vulnerability recorded for hassanameen →
FAQ
The hassanameen package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The malicious code modifies your package.json file, potentially leading to dependency confusion and the introduction of insecure packages into your application.
If you have installed the hassanameen package, it is recommended to uninstall it immediately and check for any unauthorized changes in your project.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
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.