Malicious Code Injection in asadshaikh Package - npm Vulnerability

asadshaikh Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170922: Malicious code in asadshaikh (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 asadshaikh package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation and publication of derivative packages. The vulnerability stems from the package's design, which allows for the automatic modification and republishing of its contents, leading to potential abuse within the npm registry.

Vulnerability Detail

The vulnerability in the asadshaikh package originates from its involvement in the tea.xyz token reward campaign. It contains scripts that automatically generate and publish derivative packages with randomized names, modifying the package.json file to remove private flags and changing version numbers. This behavior can lead to the pollution of the npm registry and may compromise the integrity of other packages, as well as affect developers' reputations.

How To Fix

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

npm uninstall asadshaikh

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 asadshaikh package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unintended changes in the package.json file.

Conclusion

The asadshaikh package has been identified as a malicious entity within the npm ecosystem, capable of modifying and republishing its contents to inflate developer reputation scores. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their software.

See every vulnerability recorded for asadshaikh →

Share this vulnerability

FAQ

The asadshaikh package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the automatic modification of your package.json file and the pollution of the npm registry, potentially compromising your project's integrity.

You should remove the asadshaikh package from your project immediately and monitor for any updates or patches.

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.

How To Fix

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

npm uninstall asadshaikh

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