Malicious Code Injection in Ramadan-Poke35 Package - npm Vulnerability

ramadan-poke35 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

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

Ramadan-Poke35 is an npm package that is part of a larger ecosystem of packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores in exchange for token rewards, which raises significant concerns about the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the Ramadan-Poke35 package stems from its malicious code that 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 issue is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of these malicious packages. The ramifications include potential security risks for developers who unknowingly install these packages, as well as damage to the reputation of the npm registry.

How To Fix

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

npm uninstall ramadan-poke35

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 workaround, you can avoid using the Ramadan-Poke35 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like Vulert to monitor for vulnerabilities.

Conclusion

The Ramadan-Poke35 package presents a significant vulnerability due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for similar threats. Utilizing tools like Vulert can aid in maintaining a secure development environment.

See every vulnerability recorded for ramadan-poke35 →

Share this vulnerability

FAQ

Ramadan-Poke35 is an npm package involved in a token reward campaign that generates and publishes numerous derivative packages to inflate developer reputation scores.

The vulnerability can lead to the installation of malicious code that modifies your package.json file and pollutes the npm registry, posing security risks.

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

If you have installed the Ramadan-Poke35 package, you should uninstall it immediately using npm uninstall ramadan-poke35 and check your package-lock.json file.

Yes, tools like Vulert can monitor your package-lock.json file in real-time for open-source vulnerabilities, helping you stay informed about potential risks.

How To Fix

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

npm uninstall ramadan-poke35

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