Malicious Code Injection in Screeching Newt Z3N Package

screeching_newt_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96468: Malicious code in screeching_newt_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

Screeching Newt Z3N is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm ecosystem, but it has been compromised by malicious actors. The vulnerability stems from the package's involvement in a scheme that generates and publishes derivative packages with the intent to inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the Screeching Newt Z3N package involves the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is linked to a broader campaign that aims to pollute the npm registry, potentially affecting developers' workflows and the integrity of the npm ecosystem.

How To Fix

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

npm uninstall screeching_newt_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 remove the affected package from your project by executing: npm uninstall screeching_newt_z3n. This will prevent any malicious code from executing until a fixed version is available.

Conclusion

The Screeching Newt Z3N package has been compromised with malicious code that alters critical files and republishing behavior. It is essential for developers to take immediate action by updating or removing the package to safeguard their projects and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for screeching_newt_z3n →

Share this vulnerability

FAQ

Screeching Newt Z3N is an npm package involved in the tea.xyz token reward campaign, designed to facilitate various functionalities within the npm ecosystem.

The vulnerability allows malicious code to alter your package.json file, potentially leading to unauthorized package republishing and pollution of the npm registry.

If you are using the Screeching Newt Z3N package, it is crucial to update it to a patched version or remove it from your project until a fix is available.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.

To prevent future vulnerabilities, regularly update your dependencies, utilize tools like Vulert for monitoring, and review package sources before installation.

How To Fix

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

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