Malicious code in commonweb-flow (npm)
Malicious npm package commonweb-flow published with versions 7.999.999 and 10.11.0 containing code that fetches and executes arbitrary code from an external server (artifacts.yosiroute.com) during npm install. The package exhibits dependency-confusion characteristics with inflated version numbers and placeholder metadata.
- Disclosed
- Last updated
- Blast radius
- Any developer or CI/CD system installing commonweb-flow versions 7.999.999 or 10.11.0 from npm registry
- Ecosystems
- Attack vectors
- Affected entities
- commonweb-flow · 7.999.999, 10.11.0
The npm package commonweb-flow was published with malicious intent in at least two versions: 7.999.999 and 10.11.0. Version 7.999.999 declares a direct dependency on a tarball hosted at artifacts.yosiroute.com rather than using the npm registry, with the npm-shrinkwrap.json file marking this dependency with hasInstallScript: true. This configuration causes npm to fetch and execute arbitrary code from the external host during installation.
The package exhibits characteristics of a dependency-confusion attack, including inflated version numbers (7.999.999 vs. self-reported 1.0.0), placeholder metadata (author: "Package Registry", description: "Generated package"), and a fake repository URL. This pattern suggests the package was designed to be resolved from the public npm registry in preference to an internal package of the same name.
Version 10.11.0 was independently flagged by the OpenSSF Package Analysis project as malicious due to communication with domains associated with malicious activity and execution of commands associated with malicious behavior.
The tarball contents at the external URL are mutable, allowing the attacker to modify the payload server-side without republishing the npm package, increasing the attack surface.
Indicators of compromise
- Packages
- commonweb-flow
- Domains
- artifacts.yosiroute.com
- yosiroute.com
Remediation
- Remove commonweb-flow versions 7.999.999 and 10.11.0 from all environments immediately
- Audit npm install logs and CI/CD pipelines for any installations of these versions
- Review and revoke any credentials or secrets that may have been exposed on machines that installed these packages
- Block artifacts.yosiroute.com at the network level to prevent callback attempts
- If an internal package named commonweb-flow exists, ensure it is properly scoped or published to a private registry with access controls
- Implement npm registry pinning and dependency verification to prevent dependency-confusion attacks
- Monitor for any suspicious activity or lateral movement from affected systems
Sources
- GitHub Advisory GHSA-hvpr-vw2p-qhw6 · GitHub Advisory Database
Cite this entry
"Malicious code in commonweb-flow (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 7, 2026; last updated August 7, 2026. https://supplychainattack.org/incident/malicious-code-in-commonweb-flow-npm-1a5qw0
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in mtslink-depconf-probe-profileusername (npm)
The npm package mtslink-depconf-probe-profileusername contained malicious code designed to probe for internal namespace dependencies and exfiltrate install-time telemetry via DNS lookups to attacker-controlled infrastructure. The package was identified as a dependency-confusion probe targeting internal package namespaces.
npmCompromised packageDependency confusion - containedcritical
Malicious code in ssb-test-package (npm)
ssb-test-package@1.0.0 on npm contains malicious code designed as a dependency-confusion proof-of-concept. A preinstall hook executes arbitrary code on installation, performing host reconnaissance and writing results to a local file.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in gemini-cli-a2a-server (npm)
A malicious npm package named gemini-cli-a2a-server was published to exploit dependency confusion, mimicking a private Google internal component. The postinstall script collected host identifiers and exfiltrated them to a hardcoded external endpoint.
npmDependency confusionCompromised package - containedcritical
Malicious code in gaarf-bq (npm)
The npm package gaarf-bq contained malicious code in its postinstall lifecycle script that collected and exfiltrated host identifiers to an attacker-controlled domain. The package name resembles Google's legitimate gaarf (ads-api-report-fetcher) BigQuery component, consistent with dependency-confusion tactics.
npmCompromised packageDependency confusion