Malicious Code Detected in zabittest11: npm Package Vulnerability

zabittest11 Updated 25 Jan 2026

Summary

25/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-500: Malicious code in zabittest11 (npm). Affects zabittest11 versions 1.0.1. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'zabittest11' package, version 1.0.1, is an npm package that has been identified as malicious. It is designed to perform certain functions within JavaScript applications but has been compromised to communicate with a domain associated with malicious activities. This vulnerability poses a significant risk to applications relying on this package, as it can lead to unauthorized data access or compromise system integrity.

Vulnerability Detail

The vulnerability in the 'zabittest11' package arises from its communication with a domain linked to malicious activities. This behavior indicates that the package may be involved in data exfiltration or other harmful actions that can compromise the security of applications using it. The OpenSSF Package Analysis project has flagged this package as malicious, emphasizing the importance of addressing this issue promptly to prevent potential exploitation.

How To Fix

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

npm uninstall zabittest11

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 temporarily disable any functionality that relies on the 'zabittest11' package until it is removed or replaced. This will help mitigate any immediate risks associated with its use.

Conclusion

The 'zabittest11' npm package has been identified as malicious, posing significant risks to applications that utilize it. Immediate action is required to remove this package and safeguard your application from potential threats. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for zabittest11 →

Share this vulnerability

FAQ

The 'zabittest11' package is an npm package that has been flagged as malicious due to its communication with a domain involved in harmful activities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed 'zabittest11', you should uninstall it immediately using the command 'npm uninstall zabittest11' and look for safer alternatives.

No, there are no patches available for 'zabittest11' as it has been identified as a malicious package. The best course of action is to remove it from your project.

Using malicious packages can lead to data breaches, unauthorized access to sensitive information, and potential damage to your application's integrity and reputation.

How To Fix

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

npm uninstall zabittest11

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