Malicious Code Injection in select_primate_z3n Package

select_primate_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96496: Malicious code in select_primate_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 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 select_primate_z3n package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that inflate developer reputation scores. This package, like others in the campaign, is designed to automatically generate and publish derivative packages, making it a target for malicious exploitation.

Vulnerability Detail

The vulnerability in the select_primate_z3n package originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to unauthorized access and manipulation of their projects.

How To Fix

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

npm uninstall select_primate_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, developers should avoid using the select_primate_z3n package and remove it from their projects. You can uninstall the package using the following command: npm uninstall select_primate_z3n.

Conclusion

The select_primate_z3n package has been identified as containing malicious code that can compromise the security of projects using it. It is essential for developers to take immediate action by removing the package and monitoring their applications for any unauthorized changes. Utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for select_primate_z3n →

Share this vulnerability

FAQ

The select_primate_z3n package is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The vulnerability can lead to unauthorized modifications in your project's package.json file, potentially compromising the security and integrity of your application.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground.

If you have used the select_primate_z3n package, it is crucial to uninstall it immediately and check for any unauthorized changes in your project.

Regularly audit your dependencies, use tools like Vulert for monitoring vulnerabilities, and keep your packages updated to their latest secure versions.

How To Fix

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

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