Malicious Code Injection in abedalrahman Package: npm Vulnerability Summary

abedalrahman Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170638: Malicious code in abedalrahman (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The abedalrahman package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a larger campaign that aims to manipulate the npm registry by flooding it with derivative packages. This package, like others in the campaign, is designed to inflate developer reputation scores for token rewards through automated publishing scripts.

Vulnerability Detail

The vulnerability in the abedalrahman package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages and applications relying on npm. The malicious payload can affect developers' reputations and the overall trustworthiness of the npm ecosystem.

How To Fix

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

npm uninstall abedalrahman

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, avoid using the abedalrahman package and consider utilizing alternative packages that provide similar functionality without the associated risks. Regularly monitor your dependencies for any updates or vulnerabilities.

Conclusion

The abedalrahman package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. Immediate action is required to remove this package and safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for abedalrahman →

Share this vulnerability

FAQ

The abedalrahman package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

This vulnerability can compromise the integrity of your application by introducing malicious code and affecting the reputation of your development environment.

You should uninstall the abedalrahman package immediately using the command 'npm uninstall abedalrahman' and check for any other vulnerable packages.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against this vulnerability using the Vulert playground.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by the abedalrahman 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 abedalrahman

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