Malicious Code Injection in abdalrahman113 Package: npm Vulnerability Overview

abdalrahman113 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170622: Malicious code in abdalrahman113 (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 abdalrahman113 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 exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for users.

Vulnerability Detail

The vulnerability in the abdalrahman113 package originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior allows the package to continuously republish variants, thereby polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include the risk of developers unknowingly using compromised packages, leading to security breaches in their applications.

How To Fix

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

npm uninstall abdalrahman113

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 remove the abdalrahman113 package from your project by executing the following command: npm uninstall abdalrahman113. This will prevent any malicious code from executing in your application until a safe version is available.

Conclusion

The abdalrahman113 package poses a significant security risk due to its malicious code that modifies package metadata and floods the npm registry. It is essential for developers to be vigilant about the packages they use and to implement best practices for security management.

See every vulnerability recorded for abdalrahman113 →

Share this vulnerability

FAQ

The abdalrahman113 package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

If you have installed the abdalrahman113 package, it is crucial to uninstall it immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner without any signup.

To prevent similar vulnerabilities, regularly update your packages, utilize tools like Vulert for real-time monitoring, and review package dependencies for any known issues.

How To Fix

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

npm uninstall abdalrahman113

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