Malicious Code Injection in aaseefiqbal Package: npm Vulnerability Overview

aaseefiqbal Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170613: Malicious code in aaseefiqbal (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The aaseefiqbal package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata for nefarious purposes, compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the aaseefiqbal package being part of a malicious campaign that includes scripts designed to automatically generate and publish derivative packages with randomized names. This behavior modifies the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential exploitation by malicious actors.

How To Fix

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

npm uninstall aaseefiqbal

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 workaround, you can avoid using the aaseefiqbal package altogether. If it is already installed, you can uninstall it using the command: npm uninstall aaseefiqbal. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The aaseefiqbal package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.

See every vulnerability recorded for aaseefiqbal →

Share this vulnerability

FAQ

The aaseefiqbal package is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.

This vulnerability can lead to the pollution of the npm registry, potentially allowing malicious actors to exploit your application through compromised dependencies.

You should uninstall the aaseefiqbal package immediately and monitor your project for any other vulnerable dependencies.

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

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.

How To Fix

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

npm uninstall aaseefiqbal

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