Malicious Code Detected in wepack-cli: A Critical Security Alert

wepack-cli Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-39082: Malicious code in wepack-cli (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 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

wepack-cli is a package in the npm ecosystem designed to facilitate the bundling of JavaScript applications. It offers features such as module resolution, code splitting, and asset management. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in wepack-cli stems from the inclusion of malicious code that can compromise the integrity of applications using this package. This code may lead to unauthorized access, data breaches, or even complete system takeover. The issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall wepack-cli

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, users can avoid using wepack-cli until the vulnerability is addressed. Alternatively, consider using a different package that offers similar functionality without the associated risks.

Conclusion

The discovery of malicious code in wepack-cli highlights the importance of vigilance in open-source software management. Users are urged to update their packages promptly and consider using tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for wepack-cli →

Share this vulnerability

FAQ

wepack-cli is a command-line interface for the wepack module bundler, used to bundle JavaScript applications.

The malicious code was identified by security researchers from Amazon Inspector, who reported it as part of their ongoing monitoring of open-source packages.

Using wepack-cli with the malicious code can lead to security vulnerabilities, including unauthorized access to sensitive data and potential system compromises.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If an immediate update is not possible, consider using alternative packages or temporarily disabling the functionality that relies on wepack-cli until a fix is implemented.

Related vulnerabilities

Recent vulnerabilities recorded for wepack-cli.

How To Fix

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

npm uninstall wepack-cli

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