# MAL-2025-6894: Malicious code in commonweb-flow (npm)


- **Type:** Malicious package
- **Package:** `commonweb-flow` (npm)
- **Published:** 17 Aug 2025

## What is MAL-2025-6894?

MAL-2025-6894 is a malicious package in commonweb-flow, published on 17 Aug 2025. 

### Official description

commonweb-flow@7.999.999 declares its sole dependency `linker-event-header-serial` as a direct tarball URL on `artifacts.yosiroute.com` (not the npm registry), and npm-shrinkwrap.json marks that dependency with `hasInstallScript: true`. On `npm install`, npm fetches the tarball from `artifacts.yosiroute.com` and runs its lifecycle install scripts, giving that host arbitrary code execution on the installer's machine. The tarball contents at that URL are mutable and can be swapped server-side without republishing commonweb-flow. Package metadata is placeholder (`author: "Package Registry"`, `description: "Generated package"`, repository `github.com/example/commonweb-flow`), and the manifest version `7.999.999` is inflated relative to the README/index.js self-reported `1.0.0` — the shape of a dependency-confusion lure aimed at internal builds that resolve `commonweb-flow` from the public registry over an internal package of the same name.

The OpenSSF Package Analysis project identified 'commonweb-flow' @ 10.11.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

- The package executes one or more commands associated with malicious behavior.

## What should I do about MAL-2025-6894?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2025-6894 is a malicious package: commonweb-flow (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2025-6894/ (Markdown: https://insights.sbomify.com/MAL-2025-6894/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2025-6894

---
From sbomify Insights: https://insights.sbomify.com/MAL-2025-6894/
Summaries are generated and may contain mistakes; the official description above is the record.