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

ramadan-poke1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164592: Malicious code in ramadan-poke1 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'ramadan-poke1' is part of a series of malicious npm packages that emerged during 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 is intended to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in 'ramadan-poke1' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can affect developers' projects by introducing unwanted dependencies and altering expected behaviors.

How To Fix

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

npm uninstall ramadan-poke1

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-poke1' and any packages that may depend on it. Consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your package-lock.json file for any unexpected changes.

Conclusion

The 'ramadan-poke1' package poses a significant risk to npm users due to its malicious behavior aimed at manipulating the npm registry. It is essential to remove this package from your projects and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for ramadan-poke1 →

Share this vulnerability

FAQ

'ramadan-poke1' is a malicious npm package that is part of a campaign to inflate developer reputation scores through the automatic generation and publishing of derivative packages.

You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Using 'ramadan-poke1' can lead to the introduction of unwanted dependencies, potential security vulnerabilities, and the pollution of the npm registry, which can affect other packages.

It is recommended to regularly check for vulnerabilities, ideally as part of your development workflow, to ensure that you are using secure and up-to-date packages.

You should immediately uninstall 'ramadan-poke1' and review your project for any dependencies that may have been affected. Consider using Vulert to monitor your project for further vulnerabilities.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall ramadan-poke1

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