Malicious Code Injection in jelek-rasaaya-nu: A Threat to npm Packages

jelek-rasaaya-nu Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157042: Malicious code in jelek-rasaaya-nu (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'jelek-rasaaya-nu' is part of a broader campaign that exploits the npm ecosystem, specifically targeting developers involved in the tea.xyz token reward initiative. This package is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. Its functionality includes modifying package metadata and continuously republishing variants, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'jelek-rasaaya-nu' stems from its malicious code that alters the package.json file by removing private flags and changing version numbers. This allows the package to generate random names, predominantly Indonesian-themed, and republish itself, thereby compromising the integrity of the npm registry. The origin of this vulnerability is linked to a campaign that floods the npm ecosystem with such malicious packages, which can lead to reputation damage for developers and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall jelek-rasaaya-nu

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 restrict the use of the npm registry by using a private registry or by implementing strict dependency management practices. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The 'jelek-rasaaya-nu' package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for jelek-rasaaya-nu →

Share this vulnerability

FAQ

The malicious code can lead to the pollution of the npm registry, affecting the integrity of packages and potentially compromising applications that rely on these packages.

You can use Vulert to check your package-lock.json for vulnerabilities without requiring access to the code or installation. Visit the Vulert playground at Vulert Scanner.

You should immediately uninstall the package using 'npm uninstall jelek-rasaaya-nu' and review your other dependencies for similar vulnerabilities.

It can lead to security risks and reputation damage, as your application may inadvertently rely on compromised packages.

Yes, tools like Vulert can help monitor your dependencies in real-time for open-source vulnerabilities.

How To Fix

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

npm uninstall jelek-rasaaya-nu

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