Malicious Code Injection in uaragifa-marae-saf Package - npm Vulnerability
Summary
MAL-2025-169551: Malicious code in uaragifa-marae-saf (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The uaragifa-marae-saf package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by publishing derivative packages with harmful scripts.
Vulnerability Detail
The vulnerability in the uaragifa-marae-saf package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uaragifa-marae-safIf 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 uaragifa-marae-saf package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.
Conclusion
The uaragifa-marae-saf package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your projects.
See every vulnerability recorded for uaragifa-marae-saf →
FAQ
The uaragifa-marae-saf package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
If your application uses the uaragifa-marae-saf package, it may be at risk of security breaches and could contribute to the pollution of the npm registry.
You should remove the uaragifa-marae-saf package from your project and look for alternative packages. If a patched version is available, update it using npm.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
