Malicious Code Detected in commonweb-flow Package: Vulnerability MAL-2025-6894

commonweb-flow Updated 02 Oct 2025

Summary

17/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6894: Malicious code in commonweb-flow (npm). Affects commonweb-flow versions 10.11.0 – 10.15.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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The commonweb-flow package is an npm library designed for web development, providing various functionalities to streamline the flow of web applications. However, it has been identified as malicious, particularly in version 10.11.0, due to its ability to communicate with domains associated with malicious activities and execute harmful commands.

Vulnerability Detail

The vulnerability in the commonweb-flow package arises from its malicious behavior, which includes communicating with a domain linked to harmful activities and executing commands that can compromise system integrity. This poses significant risks, including unauthorized access to sensitive data, system manipulation, and potential exploitation by attackers. The issue was identified by the OpenSSF Package Analysis project, which flagged the package as malicious based on its behavior.

How To Fix

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

npm uninstall commonweb-flow

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

If immediate updating is not feasible, consider removing the commonweb-flow package from your project until a secure version is available. You can do this by executing: npm uninstall commonweb-flow.

Conclusion

The commonweb-flow package has been flagged for malicious behavior, specifically in versions 10.11.0 to 10.15.0. Users are advised to update to the latest version or uninstall the package to mitigate risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for commonweb-flow →

Share this vulnerability

FAQ

Versions 10.11.0, 10.12.0, 10.13.0, 10.14.0, and 10.15.0 of the commonweb-flow package are identified as malicious.

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.

As a temporary measure, you can uninstall the commonweb-flow package from your project to mitigate the risk until a secure version is available.

The vulnerability was identified by the OpenSSF Package Analysis project, which specializes in analyzing packages for malicious behavior.

Using the affected package can lead to unauthorized access to sensitive data, system manipulation, and exploitation by attackers, posing significant security risks.

How To Fix

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

npm uninstall commonweb-flow

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