Malicious Code Injection in arshadabdul Package: npm Vulnerability Overview

arshadabdul Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170912: Malicious code in arshadabdul (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 arshadabdul package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the arshadabdul package, which includes scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, ultimately polluting the npm registry and potentially harming developers who rely on the integrity of the ecosystem. The malicious payload can also affect the reputation of legitimate packages and developers.

How To Fix

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

npm uninstall arshadabdul

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 arshadabdul package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The arshadabdul package has been identified as containing malicious code that poses a significant risk to the npm ecosystem. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for arshadabdul →

Share this vulnerability

FAQ

The arshadabdul package is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially affecting functionality and security.

You should uninstall the arshadabdul package immediately using 'npm uninstall arshadabdul' and check for any dependencies that may be affected.

Yes, you can use Vulert to monitor your project's dependencies for vulnerabilities in real-time without needing to access the code or installation.

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

How To Fix

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

npm uninstall arshadabdul

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