Critical Malicious Code Vulnerability in bigwebappweb Package

bigwebappweb Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15676: Malicious code in bigwebappweb (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The bigwebappweb package is an npm library designed for building web applications with a focus on modularity and ease of use. It offers various functionalities that aid developers in creating scalable web solutions. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the bigwebappweb package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall bigwebappweb

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, consider removing the bigwebappweb package from your project until a secure version is released. You can do this by executing the following command: npm uninstall bigwebappweb. Additionally, review your application for any dependencies that may rely on this package.

Conclusion

The bigwebappweb package has been identified with a critical vulnerability due to the presence of malicious code. Users are urged to take immediate action by updating or removing the package to safeguard their applications. Continuous monitoring and proactive security measures are essential to maintain application integrity.

See every vulnerability recorded for bigwebappweb →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data or facilitate other harmful activities within the application.

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 requiring any signup.

Currently, there is no specific patch version mentioned. It is advisable to monitor the package repository for updates or consider alternative packages.

If immediate updates are not feasible, consider removing the package and reviewing your application for any dependencies that might be affected.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and conduct security audits on your codebase.

How To Fix

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

npm uninstall bigwebappweb

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