Malicious Code Injection in jelek-rasismem-a: A Threat to npm Ecosystem

jelek-rasismem-a Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-157054: Malicious code in jelek-rasismem-a (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-rasismem-a' is part of a malicious campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a significant threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability arises from the presence of malicious code within the 'jelek-rasismem-a' package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, effectively polluting the npm registry. The origin of this vulnerability is traced back to a campaign that exploits npm's publishing mechanisms, posing risks such as reputation damage for developers and potential security issues 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-rasismem-a

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 measure, you can avoid using the 'jelek-rasismem-a' package and any other packages that may be part of the malicious campaign. Regularly audit your dependencies using tools like 'npm audit' to identify and mitigate risks.

Conclusion

The 'jelek-rasismem-a' package presents a significant threat to the npm ecosystem due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action should be taken to remove any affected packages to safeguard your applications.

See every vulnerability recorded for jelek-rasismem-a →

Share this vulnerability

FAQ

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

This vulnerability can lead to the pollution of the npm registry, potentially affecting the integrity of your application and causing security risks if your application relies on compromised packages.

You should uninstall the 'jelek-rasismem-a' package immediately using 'npm uninstall jelek-rasismem-a' and audit your other dependencies for any related vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground without any signup.

Yes, tools like npm audit and Vulert can help identify and alert you to malicious packages and vulnerabilities in your dependencies.

How To Fix

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

npm uninstall jelek-rasismem-a

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