Malicious Code Injection in selective_walrus_z3n: A Threat to npm Packages

selective_walrus_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96501: Malicious code in selective_walrus_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'selective_walrus_z3n' is part of a broader trend involving malicious npm packages that are designed to inflate developer reputation scores through automated publishing. These packages often contain scripts that manipulate package metadata and publish numerous derivative versions, leading to pollution of the npm registry. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in 'selective_walrus_z3n' originates from its association with the tea.xyz token reward campaign, which has been linked to malicious activities on npm. The package includes scripts that modify the package.json file, removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants that can mislead developers and compromise their applications. The malicious payload can lead to security risks, including unauthorized access to sensitive data and the potential for further exploitation within the npm ecosystem.

How To Fix

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

npm uninstall selective_walrus_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 measure, you can avoid using the 'selective_walrus_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. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'selective_walrus_z3n' package poses significant risks due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to be vigilant about the packages they use and to regularly check for vulnerabilities. Uninstalling this package and utilizing monitoring tools like Vulert can help maintain the integrity and security of your applications.

See every vulnerability recorded for selective_walrus_z3n →

Share this vulnerability

FAQ

'selective_walrus_z3n' is an npm package that has been identified as malicious, designed to manipulate package metadata and inflate developer reputation scores.

The vulnerability can lead to unauthorized modifications of your project's dependencies, potentially exposing your application to security risks and instability.

You should uninstall the package immediately using 'npm uninstall selective_walrus_z3n' to mitigate any risks associated with its use.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit https://vulert.com for more information.

Yes, consider looking for other npm packages that provide similar functionality but are verified and trusted to avoid security risks.

How To Fix

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

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