Malicious Code Vulnerability in structural_narwhal_z3n Package

structural_narwhal_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96823: Malicious code in structural_narwhal_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 structural_narwhal_z3n package is part of the npm ecosystem and has been identified as a component of a token reward campaign associated with tea.xyz. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been compromised to include malicious scripts that alter package metadata and republish variants to the npm registry, potentially affecting developers and users relying on this package.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the structural_narwhal_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The malicious payload is part of a broader scheme to exploit the npm ecosystem, which can result in reputational damage for developers and security risks for users who inadvertently install these compromised packages.

How To Fix

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

npm uninstall structural_narwhal_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 structural_narwhal_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time by analyzing your package-lock.json file.

Conclusion

The structural_narwhal_z3n package contains malicious code that poses a significant risk to developers and users within the npm ecosystem. It is crucial to uninstall this package and monitor your project for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for structural_narwhal_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry with compromised packages.

You should uninstall the structural_narwhal_z3n package immediately and monitor your project for any unusual behavior.

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

Regularly monitor your dependencies using tools like Vulert, keep your packages updated, 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 structural_narwhal_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