Malicious Code Injection in ahmedzaid Package: npm Vulnerability Overview

ahmedzaid Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170710: Malicious code in ahmedzaid (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 ahmedzaid package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages designed to inflate developer reputation scores. This package, like others in the campaign, is vulnerable to exploitation due to its inclusion of autopublish scripts that can manipulate package metadata.

Vulnerability Detail

The vulnerability in the ahmedzaid package originates from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they can compromise the integrity of their applications and lead to reputational damage.

How To Fix

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

npm uninstall ahmedzaid

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 ahmedzaid package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The ahmedzaid package poses a significant risk due to its malicious code that alters package metadata and can lead to security vulnerabilities. It is crucial for developers to remove this package and monitor their dependencies for any potential threats. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for ahmedzaid →

Share this vulnerability

FAQ

The ahmedzaid package is an npm package linked to the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies package metadata, potentially leading to security vulnerabilities and the pollution of the npm registry.

You should uninstall the ahmedzaid package immediately using 'npm uninstall ahmedzaid' and review your project's dependencies for any other potentially malicious packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.

Yes, look for well-reviewed and actively maintained packages that provide similar functionality without the associated risks of malicious code.

How To Fix

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

npm uninstall ahmedzaid

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