Malicious Code Injection in ahmarrahman Package: npm Vulnerability Overview

ahmarrahman Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170703: Malicious code in ahmarrahman (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 ahmarrahman package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages. The vulnerability stems from the package's design, which allows it to execute scripts that modify its own metadata and republish itself under various names, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in the ahmarrahman package originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to the proliferation of malicious packages in the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.

How To Fix

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

npm uninstall ahmarrahman

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 ahmarrahman package until a fixed version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The ahmarrahman package poses a significant risk due to its malicious behavior of modifying its own metadata and republishing itself. It is crucial for developers to stay informed about such vulnerabilities and take necessary actions to protect their projects. Regular updates and monitoring tools like Vulert can help mitigate these risks.

See every vulnerability recorded for ahmarrahman →

Share this vulnerability

FAQ

The ahmarrahman package is an npm package that is suspected to be involved in a malicious campaign aimed at inflating developer reputation scores.

The vulnerability can lead to the proliferation of malicious packages in the npm registry, potentially compromising your project's dependencies and security.

If you have installed the ahmarrahman package, it is advisable to remove it and monitor for any updates or patches that may address the vulnerability.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing 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 ahmarrahman

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