Malicious Code Injection in ahnafmasood Package: npm Vulnerability Overview
Summary
MAL-2025-170713: Malicious code in ahnafmasood (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 ahnafmasood package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages typically contain scripts designed to manipulate package metadata and inflate developer reputation scores through the tea.xyz token reward system.
Vulnerability Detail
The vulnerability in the ahnafmasood package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of applications that depend on these packages. The malicious payload is designed to execute scripts that can automatically publish these variants, making it difficult for developers to maintain clean and secure package dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ahnafmasoodIf 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 ahnafmasood package and replace it with a trusted alternative. Additionally, you can use tools like Vulert to monitor your package-lock.json file for vulnerabilities. This can help you identify and mitigate risks associated with malicious packages.
Conclusion
The ahnafmasood package poses a significant risk due to its malicious behavior of modifying package metadata and flooding the npm registry. It is essential for developers to be vigilant about the packages they use and to regularly monitor for vulnerabilities. By removing affected packages and utilizing tools like Vulert, developers can help safeguard their applications from potential threats.
See every vulnerability recorded for ahnafmasood →
FAQ
The ahnafmasood package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
This vulnerability can lead to the pollution of your npm dependencies, potentially introducing malicious code into your application and compromising its security.
You should immediately uninstall the ahnafmasood package and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for 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.
