Malicious Code Injection in thin_blackbird_z3n: A Threat to npm Ecosystem

thin_blackbird_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98963: Malicious code in thin_blackbird_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 package thin_blackbird_z3n is part of the npm ecosystem, which is widely used for managing JavaScript packages. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in thin_blackbird_z3n stems from its association with a malicious token reward campaign that generates and publishes numerous derivative packages with randomized names. This behavior is facilitated by scripts that modify the package.json file, removing private flags, altering version numbers, and continuously republishing variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a negative impact on the reputation of legitimate packages.

How To Fix

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

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

Conclusion

The thin_blackbird_z3n package poses a significant threat due to its malicious code injection, which can compromise the npm ecosystem. It is essential for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications.

See every vulnerability recorded for thin_blackbird_z3n →

Share this vulnerability

FAQ

thin_blackbird_z3n is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

If you have used thin_blackbird_z3n, it is crucial to remove it from your project and update to a secure version or use an alternative package.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

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