Malicious Code Vulnerability in rigid_pinniped_0xrequest Package

rigid_pinniped_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108110: Malicious code in rigid_pinniped_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 rigid_pinniped_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the generation and publication of derivative packages. However, it has been identified as containing malicious scripts that compromise its integrity and the security of applications relying on it.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in developers unknowingly using compromised packages, which can have severe implications for application security and integrity.

How To Fix

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

npm uninstall rigid_pinniped_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 avoid using the rigid_pinniped_0xrequest package altogether. If it is a dependency of another package, consider removing that package or replacing it with a more secure alternative.

Conclusion

The rigid_pinniped_0xrequest package contains malicious code that poses a significant risk to application security. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your software.

See every vulnerability recorded for rigid_pinniped_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file and can lead to the use of compromised packages, affecting your application's security.

You should remove the rigid_pinniped_0xrequest package from your project and check for any dependencies that may rely on it.

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall rigid_pinniped_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