Malicious Code Vulnerability in printed_squirrel_z3n Package

printed_squirrel_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89518: Malicious code in printed_squirrel_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 printed_squirrel_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been identified to contain malicious code that modifies package.json files and republishes variants to pollute the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the printed_squirrel_z3n package, which is part of a broader scheme to exploit the npm registry. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This can lead to significant ramifications, including the compromise of project integrity, pollution of the npm registry, and potential security risks for developers who unknowingly use these packages.

How To Fix

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

npm uninstall printed_squirrel_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 workaround, you can monitor your project's dependencies using tools like Vulert. By utilizing Vulert, you can check if your application is affected by this vulnerability without requiring access to the code or installation. Use the Vulert playground at https://vulert.com/scanner to analyze your package-lock.json file for vulnerabilities.

Conclusion

The printed_squirrel_z3n package contains a serious vulnerability that can affect the integrity of your projects. It is crucial to remove this package and monitor your dependencies for any potential threats. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your open-source software.

See every vulnerability recorded for printed_squirrel_z3n →

Share this vulnerability

FAQ

The printed_squirrel_z3n package is an npm package associated with a token reward campaign that generates and publishes derivative packages.

The vulnerability can compromise your project's integrity by introducing malicious code and polluting the npm registry with unwanted packages.

You should uninstall the printed_squirrel_z3n package immediately and monitor your dependencies for any further vulnerabilities.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review packages before adding them to your project.

How To Fix

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

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