Malicious Code Injection in aazadhashim Package: npm Vulnerability

aazadhashim Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170617: Malicious code in aazadhashim (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The aazadhashim package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. This package is linked to the tea.xyz token reward initiative, which incentivizes developers to inflate their reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the aazadhashim package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The ramifications include loss of control over package versions, exposure to further vulnerabilities, and damage to developer reputation.

How To Fix

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

npm uninstall aazadhashim

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 prevent the installation of the aazadhashim package by using the following command to uninstall it: npm uninstall aazadhashim. Additionally, consider using npm audit to identify and address other vulnerabilities in your project.

Conclusion

The aazadhashim package poses a significant risk due to its malicious code that alters project files and floods the npm registry. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for aazadhashim →

Share this vulnerability

FAQ

The aazadhashim package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the modification of your package.json file, potentially exposing your project to further risks and compromising its integrity.

You should uninstall the aazadhashim package immediately and monitor your project for any other vulnerabilities.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall aazadhashim

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