Malicious Code Injection in assistant_bear_z3n Package

assistant_bear_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93282: Malicious code in assistant_bear_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The assistant_bear_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, this package has been identified as containing malicious code that modifies its own package.json file and repurposes it for nefarious activities.

Vulnerability Detail

The vulnerability in the assistant_bear_z3n package stems from its inclusion in a series of malicious packages that flood the npm registry. The malicious code is designed to remove private flags from package.json, alter version numbers, and generate random names for derivative packages. This behavior not only compromises the integrity of the affected package but also pollutes the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall assistant_bear_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 workaround, you can avoid using the assistant_bear_z3n package altogether. If it is already included in your project, remove it by running: npm uninstall assistant_bear_z3n. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The assistant_bear_z3n package has been identified as containing malicious code that compromises its integrity and poses risks to developers. It is crucial to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for assistant_bear_z3n →

Share this vulnerability

FAQ

The assistant_bear_z3n package is an npm package that is part of a token reward campaign, designed to automatically generate and publish derivative packages.

The malicious code modifies your package.json file, removes private flags, and can lead to the publication of compromised packages, which may pose security risks.

You should uninstall the assistant_bear_z3n package immediately and monitor your project for any other potentially compromised packages.

Yes, you can use Vulert to check your package-lock.json for vulnerabilities without needing to install any additional software.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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