Malicious Code Injection in AmeenHassan Package: npm Vulnerability Alert

ameenhassan Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170803: Malicious code in ameenhassan (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The AmeenHassan package is a part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of JavaScript code. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages, designed to inflate developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the AmeenHassan package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The intent is to continuously republish these variants, thereby polluting the npm registry and compromising the integrity of the ecosystem. This poses significant risks, including the potential for developers to unknowingly install compromised packages, 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 ameenhassan

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 avoid using the AmeenHassan package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider implementing strict package auditing practices to identify and mitigate vulnerabilities in your dependencies.

Conclusion

The AmeenHassan package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their applications from such vulnerabilities.

See every vulnerability recorded for ameenhassan →

Share this vulnerability

FAQ

AmeenHassan is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through deceptive practices.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner without any signup.

If you have installed the AmeenHassan package, you should uninstall it immediately using the command npm uninstall ameenhassan and review your project's dependencies for any other potential vulnerabilities.

Yes, you should look for alternative packages that offer similar functionality without the associated risks. Always ensure to review the package's reputation and community feedback before installation.

To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ameenhassan

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback