Malicious Code Injection in verbal_snipe_z3n Package - npm Vulnerability

verbal_snipe_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91755: Malicious code in verbal_snipe_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 verbal_snipe_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions within the npm registry but has been compromised to include malicious scripts that can manipulate package metadata. The vulnerability stems from the package's ability to modify its own package.json file, leading to potential security risks for developers and users relying on this package.

Vulnerability Detail

The vulnerability in the verbal_snipe_z3n package originates from its inclusion in a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names, which can lead to registry pollution and misuse of the npm ecosystem. This can result in developers inadvertently using compromised packages, exposing their applications to further vulnerabilities.

How To Fix

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

npm uninstall verbal_snipe_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 verbal_snipe_z3n package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The verbal_snipe_z3n package has been identified as containing malicious code that can compromise applications using it. Developers are advised to update their packages and monitor for vulnerabilities to maintain the security of their applications. Utilizing tools like Vulert can aid in identifying and mitigating such risks effectively.

See every vulnerability recorded for verbal_snipe_z3n →

Share this vulnerability

FAQ

verbal_snipe_z3n is an npm package that was part of a malicious campaign aimed at manipulating developer reputation scores through automated package publishing.

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

If you have installed the verbal_snipe_z3n package, it is recommended to remove it and update your dependencies to ensure your application is secure.

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 needing to sign up.

How To Fix

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

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