Malicious Code Injection in wee_pinniped_z3n Package

wee_pinniped_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110789: Malicious code in wee_pinniped_z3n (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

The wee_pinniped_z3n 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 various scripts that automate the generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the npm registry.

Vulnerability Detail

The vulnerability in the wee_pinniped_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for rewards, leading to pollution of the npm registry and potential security risks for users who inadvertently install these compromised packages. The origin of this issue is linked to a broader trend of malicious packages flooding the npm ecosystem, specifically targeting users seeking token rewards.

How To Fix

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

npm uninstall wee_pinniped_z3n

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 wee_pinniped_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The wee_pinniped_z3n package has been identified as containing malicious code that poses significant risks to users and the npm ecosystem. It is crucial to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for wee_pinniped_z3n →

Share this vulnerability

FAQ

The wee_pinniped_z3n package is part of the npm ecosystem and is involved in the tea.xyz token reward campaign, which automates the generation of derivative packages.

The vulnerability can lead to the installation of malicious packages that compromise your project's integrity and can potentially expose sensitive data or lead to further security issues.

You should immediately uninstall the wee_pinniped_z3n package and monitor your project for any other vulnerabilities using tools like Vulert.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid installing packages from untrusted sources.

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

How To Fix

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

npm uninstall wee_pinniped_z3n

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