Malicious Code Injection in uaragifa-at-safar Package
Summary
MAL-2025-169528: Malicious code in uaragifa-at-safar (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
Background
The uaragifa-at-safar package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package appears to be related to generating and publishing derivative packages, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the uaragifa-at-safar package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes these variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may lead to security breaches or reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uaragifa-at-safarIf 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-at-safar package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any dependencies that may inadvertently include this package.
Conclusion
The uaragifa-at-safar package has been identified as a malicious package that modifies essential metadata and repopulates the npm registry with compromised versions. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for uaragifa-at-safar →
FAQ
The uaragifa-at-safar package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner.
If you have installed the uaragifa-at-safar package, you should uninstall it immediately using npm uninstall uaragifa-at-safar and check for any dependencies that may rely on it.
Yes, using compromised packages can lead to security vulnerabilities, data breaches, and damage to your project's reputation. It is crucial to regularly audit your dependencies.
To prevent similar vulnerabilities, regularly update your packages, use tools like Vulert for monitoring, and review your dependencies for any known vulnerabilities.
