# MAL-2026-5697: Malicious code in web-model-bridge (npm)


- **Type:** Malicious package
- **Package:** `web-model-bridge` (npm)
- **Published:** 12 Jun 2026
- **Also known as:** GHSA-69cw-2vc8-9jm7

## What is MAL-2026-5697?

MAL-2026-5697 is a malicious package in web-model-bridge, published on 12 Jun 2026. 

### Official description

On `npm install`, postinstall.js sends an HTTPS POST to https://ddactic-lab.online/sc/beacon carrying the package name/version, Node version, OS, CI-detection result, and the GITHUB_REPOSITORY, GITHUB_REPOSITORY_OWNER, and GITHUB_WORKFLOW environment variables when present. A DNS-lookup fallback encodes the same identifiers as a subdomain under `*.b.ddactic-lab.online` so the leak still completes even when HTTP egress is filtered — a pattern intended specifically to defeat egress controls. The package itself is a hollow placeholder: package.json describes it as an `npm 404 error` reference and index.js does nothing but `require('web-model-bridge')` (its own name) inside a try/catch, so the only effect of installing it is the install-time beacon. Any CI pipeline whose dependency tree references this name will leak the owning GitHub org/repo/workflow identity to an unrelated third-party domain on every build.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-5697?

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-2026-5697 is a malicious package: web-model-bridge (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-2026-5697/ (Markdown: https://insights.sbomify.com/MAL-2026-5697/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5697

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