Malicious Code Injection in adnansafwan Package: npm Vulnerability Overview

adnansafwan Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170672: Malicious code in adnansafwan (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 adnansafwan 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 often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the adnansafwan package stems from its inclusion in 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 these variants, which pollutes the npm registry and can compromise the security and reliability of applications that depend on these packages. The malicious payload is designed to execute scripts that automate the publication of these harmful packages, thereby increasing the risk of dependency confusion and supply chain attacks.

How To Fix

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

npm uninstall adnansafwan

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 adnansafwan package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.

Conclusion

The adnansafwan package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can enhance your ability to monitor for vulnerabilities in real-time, ensuring the security of your applications.

See every vulnerability recorded for adnansafwan →

Share this vulnerability

FAQ

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

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

You should uninstall the adnansafwan package immediately using the command npm uninstall adnansafwan.

Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software without requiring access to the code.

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 adnansafwan

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