Malicious Code Vulnerability in strong_orca_z3n Package

strong_orca_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98950: Malicious code in strong_orca_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The strong_orca_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the generation and publication of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability in the strong_orca_z3n package originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry and potential exploitation by attackers. This behavior not only inflates developer reputation scores but also poses a significant risk to users who may unknowingly install compromised packages.

How To Fix

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

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

Conclusion

The strong_orca_z3n package contains a significant vulnerability due to malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to update or remove this package to safeguard their applications and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for strong_orca_z3n →

Share this vulnerability

FAQ

The strong_orca_z3n package is part of the npm ecosystem and is linked to the tea.xyz token reward campaign, which aims to generate and publish derivative packages.

The malicious code modifies your package.json file, potentially exposing your application to security risks and polluting the npm registry with compromised packages.

If you have installed the strong_orca_z3n package, it is recommended to update it to the latest version or remove it from your project until a secure version is available.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Detailed information about this vulnerability can be found in the official npm registry or by checking the package's repository on GitHub.

How To Fix

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

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