Malicious Code Injection in nudela-rahfeg-gsa: A Threat to npm Users

nudela-rahfeg-gsa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163838: Malicious code in nudela-rahfeg-gsa (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

nudela-rahfeg-gsa is an npm package that has been identified as part of a malicious campaign targeting developers. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with harmful packages. The primary function of this package is to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, its malicious nature poses significant risks to users and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in nudela-rahfeg-gsa stems from its design to execute autopublish scripts that modify the package.json file by removing private flags and altering version numbers. This behavior allows the package to generate random names, often themed around Indonesian culture, and continuously republish these variants, thereby polluting the npm registry. The implications of this vulnerability include potential security risks for developers who unknowingly use these packages, as well as the degradation of the npm registry's reliability.

How To Fix

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

npm uninstall nudela-rahfeg-gsa

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 nudela-rahfeg-gsa package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The nudela-rahfeg-gsa package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for nudela-rahfeg-gsa →

Share this vulnerability

FAQ

nudela-rahfeg-gsa is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and the integrity of your application.

You should uninstall the nudela-rahfeg-gsa package immediately and check your project for any other potentially harmful packages.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this 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 nudela-rahfeg-gsa

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