Malicious Code Injection in live_shark_z3n Package: A Threat to npm Ecosystem

live_shark_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105274: Malicious code in live_shark_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The live_shark_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits the npm registry, leading to significant security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the live_shark_z3n package stems from its association with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to pollution of the npm registry and potential exploitation of applications that depend on these packages.

How To Fix

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

npm uninstall live_shark_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 measure, avoid using the live_shark_z3n package and monitor your dependencies for any malicious activity. You can also use tools like Vulert to check for vulnerabilities in your application without needing to access the code directly.

Conclusion

The live_shark_z3n package poses a significant threat to the npm ecosystem due to its malicious code that can compromise applications. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to ensure their applications remain secure.

See every vulnerability recorded for live_shark_z3n →

Share this vulnerability

FAQ

The live_shark_z3n package is a JavaScript package available on npm, which has been identified as part of a malicious campaign.

The vulnerability can lead to the pollution of the npm registry and may expose your application to further security risks if it relies on compromised packages.

You should uninstall the live_shark_z3n package immediately and monitor your project for any other potentially malicious dependencies.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring a signup.

Vulert is a service that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights into potential security issues.

How To Fix

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

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