Malicious Code Injection in testy_blackbird_z3n Package

testy_blackbird_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109565: Malicious code in testy_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 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 testy_blackbird_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 npm's publishing capabilities to inflate developer reputation scores through the creation of numerous derivative packages.

Vulnerability Detail

The vulnerability in the testy_blackbird_z3n package stems from its involvement in a malicious campaign aimed at generating and publishing numerous derivative packages with randomized names. This is achieved through scripts that modify the package.json file to remove private flags, alter version numbers, and continuously republish variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and the undermining of trust in the npm ecosystem.

How To Fix

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

npm uninstall testy_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 measure, you can avoid using the testy_blackbird_z3n package and any other packages that may be part of the malicious campaign. Regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The testy_blackbird_z3n package has been identified as a malicious package that poses significant risks to developers and the npm ecosystem. It is crucial to remove this package from your projects and regularly audit your dependencies to maintain a secure development environment.

See every vulnerability recorded for testy_blackbird_z3n →

Share this vulnerability

FAQ

The testy_blackbird_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of numerous derivative packages.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without requiring access to the code or installation.

Using the testy_blackbird_z3n package poses risks such as exposure to malicious code, pollution of the npm registry, and potential security vulnerabilities in your application.

It is recommended to audit your npm packages regularly, ideally after every major update or installation of new packages, to ensure that you are not using any vulnerable dependencies.

If you find a vulnerability in one of your packages, you should immediately remove the affected package, update to a patched version if available, and consider using alternative packages that are known to be secure.

How To Fix

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

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