Malicious Code Injection in interesting_puma_0xrequest Package

interesting_puma_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104329: Malicious code in interesting_puma_0xrequest (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 interesting_puma_0xrequest package is part of the npm ecosystem, often used for various JavaScript applications. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package, like others in the campaign, contains scripts designed to manipulate its own metadata and publish variants with altered names.

Vulnerability Detail

This vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, changes version numbers, and generates random package names, leading to pollution of the npm registry. This can result in compromised developer reputations and potential security risks 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 interesting_puma_0xrequest

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 temporarily avoid using the interesting_puma_0xrequest package and replace it with a trusted alternative. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The interesting_puma_0xrequest package has been identified as containing malicious code that poses a risk to developers and their applications. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your projects.

See every vulnerability recorded for interesting_puma_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been found to contain malicious code as part of a campaign to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application if it relies on this package.

You should remove the interesting_puma_0xrequest package from your project and replace it with a trusted alternative.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

npm uninstall interesting_puma_0xrequest

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