Malicious Code Injection in reasonable_gull_z3n Package

reasonable_gull_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96219: Malicious code in reasonable_gull_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The reasonable_gull_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages often contain scripts that manipulate package metadata for nefarious purposes, impacting developers and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the reasonable_gull_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The ramifications include potential pollution of the npm registry and compromise of developer environments.

How To Fix

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

npm uninstall reasonable_gull_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 reasonable_gull_z3n package from your project by executing: npm uninstall reasonable_gull_z3n. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The reasonable_gull_z3n package poses a significant risk due to its malicious code that alters package metadata. It is crucial for developers to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for reasonable_gull_z3n →

Share this vulnerability

FAQ

reasonable_gull_z3n is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to unauthorized modifications of your package.json file and potentially compromise your development environment.

You should uninstall the package immediately and monitor for any updates or patches that may be released.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access. Visit Vulert Scanner to check if your application is affected.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security practices in the open-source community.

How To Fix

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

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