Malicious Code Injection in jelek-ras-batub: A Threat to npm Users

jelek-ras-batub Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157033: Malicious code in jelek-ras-batub (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 Your last release was probably never penetration tested 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-ras-batub' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior aims to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'jelek-ras-batub' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the security of the affected packages but also affects the overall trustworthiness of the npm ecosystem, leading to potential exploitation by malicious actors.

How To Fix

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

npm uninstall jelek-ras-batub

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 'jelek-ras-batub' package and monitor your package-lock.json file for any unauthorized changes. If you suspect that your project has been compromised, consider reverting to a previous version of your project before the installation of this package.

Conclusion

The 'jelek-ras-batub' package poses a significant threat to npm users due to its malicious behavior of modifying package files and flooding the npm registry. It is essential to uninstall this package and monitor your project for any vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for jelek-ras-batub →

Share this vulnerability

FAQ

The 'jelek-ras-batub' package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the automatic generation of derivative packages.

This vulnerability can compromise the integrity of your project by introducing malicious code that modifies your package.json file and floods the npm registry with unauthorized packages.

You should immediately uninstall the package using 'npm uninstall jelek-ras-batub' and review your project for any unauthorized changes.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall jelek-ras-batub

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