Malicious Code Injection in selected_quokka_z3n Package

selected_quokka_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96498: Malicious code in selected_quokka_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 selected_quokka_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to significant risks for developers and their projects.

Vulnerability Detail

The vulnerability in the selected_quokka_z3n package stems from its association with a malicious campaign that generates and publishes derivative packages with randomized names. This is done through autopublish scripts that modify the package.json file to remove private flags and change version numbers. The malicious payload can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising their applications with untrusted code.

How To Fix

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

npm uninstall selected_quokka_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 selected_quokka_z3n package until a fix is released. Additionally, you can monitor your package-lock.json file for any changes that may indicate the presence of malicious packages. Use the following command to remove the package: npm uninstall selected_quokka_z3n.

Conclusion

The selected_quokka_z3n package has been identified as part of a malicious campaign that poses a significant risk to developers using npm. It is crucial to take immediate action by updating or removing the package to safeguard your applications from potential threats.

See every vulnerability recorded for selected_quokka_z3n →

Share this vulnerability

FAQ

The selected_quokka_z3n package is an npm package that is part of a malicious campaign aimed at exploiting the npm registry.

This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and functionality.

If you have installed the selected_quokka_z3n package, you should uninstall it immediately and monitor your project for any signs of malicious activity.

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

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 selected_quokka_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