Malicious Code Injection in ramadan-poke38: A Threat to npm Users

ramadan-poke38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164623: Malicious code in ramadan-poke38 (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

ramadan-poke38 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to alter its own metadata and proliferate harmful variants across the registry.

Vulnerability Detail

The vulnerability in ramadan-poke38 stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random Indonesian-themed package names and continuously republishes these variants, leading to pollution of the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall ramadan-poke38

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 ramadan-poke38 and any packages that depend on it. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The ramadan-poke38 package poses a significant threat to the npm ecosystem due to its malicious behavior of altering package metadata and proliferating harmful variants. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for ramadan-poke38 →

Share this vulnerability

FAQ

ramadan-poke38 is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through the automatic generation of harmful package variants.

The vulnerability can lead to the installation of malicious code that compromises your project's security and integrity, potentially allowing unauthorized access or data breaches.

You should immediately remove the ramadan-poke38 package from your project and check for any other affected packages. Use npm uninstall ramadan-poke38 to remove it.

You can use tools like npm audit to scan your project for vulnerabilities. Additionally, consider using Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json.

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

How To Fix

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

npm uninstall ramadan-poke38

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