Malicious Code Injection in complex_sawfish_z3n Package

complex_sawfish_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100775: Malicious code in complex_sawfish_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 complex_sawfish_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. It is often utilized for various functionalities within applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts designed to manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the complex_sawfish_z3n package stems from its association with the tea.xyz token reward campaign. This package contains scripts that automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to significant security risks for developers and users relying on this package.

How To Fix

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

npm uninstall complex_sawfish_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 prevent the installation of this package by using npm's package-lock.json file to lock dependencies. Ensure that your project does not include complex_sawfish_z3n in its dependencies.

Conclusion

The complex_sawfish_z3n package poses a significant security risk due to its malicious code designed to manipulate npm registry data. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for complex_sawfish_z3n →

Share this vulnerability

FAQ

The complex_sawfish_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate package metadata and inflate developer reputation scores.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and exposing it to security risks.

You should remove the complex_sawfish_z3n package from your project and monitor for any updates or patches that may address this vulnerability.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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