Malicious Code Injection in uaragifa-maranfu-safar: A Threat to npm Packages

uaragifa-maranfu-safar Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169563: Malicious code in uaragifa-maranfu-safar (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

uaragifa-maranfu-safar is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to manipulate package metadata and inflate developer reputation scores through automated scripts. Its primary function is to serve as a token reward mechanism, but it has been compromised to include harmful code that can affect developers and their projects.

Vulnerability Detail

The vulnerability in uaragifa-maranfu-safar stems from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names and continuously republishes variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, leading to potential data breaches or further exploitation.

How To Fix

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

npm uninstall uaragifa-maranfu-safar

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, consider using a package-lock.json file to lock your dependencies to known safe versions. This can help prevent the installation of compromised packages. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json for real-time alerts on open-source vulnerabilities.

Conclusion

The uaragifa-maranfu-safar package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for uaragifa-maranfu-safar →

Share this vulnerability

FAQ

uaragifa-maranfu-safar is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the installation of malicious code that compromises your project's integrity and security.

You should uninstall the package immediately using npm uninstall uaragifa-maranfu-safar and monitor your project for any signs of compromise.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and ensure you are using trusted packages.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall uaragifa-maranfu-safar

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