Malicious Code Injection in ramadan-poke37: A Threat to npm Ecosystem

ramadan-poke37 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164622: Malicious code in ramadan-poke37 (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 'ramadan-poke37' is part of a series of malicious npm packages linked to 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, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'ramadan-poke37' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry. The ramifications include compromised package integrity, potential security risks for users, and a degraded developer experience due to the cluttered registry.

How To Fix

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

npm uninstall ramadan-poke37

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 'ramadan-poke37' package and monitor your project for any dependencies that may indirectly include it. Regularly audit your package-lock.json file to identify and remove any malicious packages.

Conclusion

The 'ramadan-poke37' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the registry. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity and security of their applications.

See every vulnerability recorded for ramadan-poke37 →

Share this vulnerability

FAQ

'ramadan-poke37' is a malicious npm package that is part of a campaign to manipulate the npm registry by publishing derivative packages.

The vulnerability can lead to compromised package integrity, security risks, and a cluttered npm registry, which can affect the overall performance and reliability of your project.

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

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

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-poke37

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