Malicious Code Injection in superior_constrictor_z3n: A Threat to npm Packages

superior_constrictor_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109310: Malicious code in superior_constrictor_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 package 'superior_constrictor_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated scripts that publish variants with randomized names.

Vulnerability Detail

The vulnerability in 'superior_constrictor_z3n' originates from its association with the tea.xyz token reward campaign. It contains malicious payloads that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of other packages.

How To Fix

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

npm uninstall superior_constrictor_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 malicious package by using npm's package-lock.json file to monitor your dependencies. If you are using Vulert, you can check your application for vulnerabilities without any signup by visiting the Vulert playground at https://vulert.com/scanner.

Conclusion

The 'superior_constrictor_z3n' package poses a significant threat due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remain vigilant and take proactive measures to secure their applications by removing such packages and utilizing tools like Vulert for ongoing monitoring.

See every vulnerability recorded for superior_constrictor_z3n →

Share this vulnerability

FAQ

'superior_constrictor_z3n' is an npm package identified as part of a malicious campaign that floods the npm registry with derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.

You can use Vulert to monitor your application for vulnerabilities in real-time by analyzing your package-lock.json file.

You should uninstall the 'superior_constrictor_z3n' package immediately and review your dependencies for any other potentially malicious packages.

There is no patch for 'superior_constrictor_z3n' as it is recommended to remove the package entirely from your project.

How To Fix

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

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