Malicious Code Vulnerability in zip.js-2.8.2 Package

zip.js-2.8.2 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1881: Malicious code in zip.js-2.8.2 (npm). Affects zip.js-2.8.2 versions 99.0.0. 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

zip.js-2.8.2 is a JavaScript library used for handling ZIP file operations in web applications. It allows developers to create, read, and manipulate ZIP files directly in the browser. This package is widely utilized due to its ease of use and efficiency in file handling. However, the version 2.8.2 has been identified to contain malicious code, posing significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability in zip.js-2.8.2 stems from the inclusion of malicious code that can compromise the security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or even complete system takeover. The origin of this vulnerability is linked to a malicious package upload, which has been documented in the Open Source Vulnerability database. Users of this package are at risk of severe ramifications if they do not take immediate action to mitigate this threat.

How To Fix

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

npm uninstall zip.js-2.8.2

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, if you cannot update the package immediately, consider removing the zip.js-2.8.2 dependency from your project until a secure version is available. This can be done by running: npm uninstall zip.js-2.8.2. However, be aware that this may affect the functionality of your application that relies on this library.

Conclusion

The zip.js-2.8.2 package has been identified to contain malicious code that poses significant risks to applications. It is essential for developers to update to the latest version to protect their applications from potential threats. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for zip.js-2.8.2 →

Share this vulnerability

FAQ

zip.js-2.8.2 is a JavaScript library for creating and manipulating ZIP files in web applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using this package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

As a temporary measure, you can uninstall the zip.js-2.8.2 package from your project to mitigate the risk.

Detailed information about this vulnerability can be found in the Open Source Vulnerability database and on GitHub.

How To Fix

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

npm uninstall zip.js-2.8.2

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