Malicious Code Injection in public_koala_z3n Package

public_koala_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107416: Malicious code in public_koala_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 public_koala_z3n package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the publication of JavaScript packages. However, this package has been identified as malicious, containing scripts that manipulate its own metadata and publish numerous derivative packages to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the public_koala_z3n package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs such tactics to exploit npm's publishing mechanisms.

How To Fix

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

npm uninstall public_koala_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, avoid using the public_koala_z3n package and monitor your project for any unintended dependencies that may have been introduced. You can also use the following command to check for vulnerabilities in your project: npm audit.

Conclusion

The public_koala_z3n package poses a significant risk due to its malicious code that modifies package metadata and republish variants. It is crucial to remove this package from your project and monitor for any related vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for public_koala_z3n →

Share this vulnerability

FAQ

The public_koala_z3n package is an npm package that has been identified as malicious, designed to manipulate package metadata and publish numerous derivative packages.

The malicious code can compromise your project's integrity by inflating developer reputation scores and polluting the npm registry with unwanted packages.

If you have installed the public_koala_z3n package, you should uninstall it immediately using the command: npm uninstall public_koala_z3n.

Yes, you can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software without requiring code access.

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