# MAL-2026-14445: Malicious code in digitalexp-style-module-l9 (npm)


- **Type:** Malicious package
- **Package:** `digitalexp-style-module-l9` (npm)
- **Published:** 25 Aug 2026
- **Also known as:** GHSA-r7fr-v3m3-mpq2

## What is MAL-2026-14445?

MAL-2026-14445 is a malicious package in digitalexp-style-module-l9, published on 25 Aug 2026. 

### Official description

package.json declares both preinstall and postinstall as `node beacon.js`, so beacon.js runs automatically on every `npm install`. beacon.js reads os.hostname(), os.userInfo().username, process.cwd(), and the package name, hex-encodes the collected string, splits it into <=60-char DNS labels, and issues a DNS lookup against those labels under the author-controlled domain b0.rs. It additionally issues an HTTPS GET to https://b0.rs/?poc=...&host=...&cwd=... carrying the same fields in the query string. A source comment identifies the DNS-tunnel channel as chosen for its 'best chance of escaping egress-filtered CI', confirming the dual-channel design is intentional evasion. The version number 99.0.0 is consistent with a dependency-confusion payload targeting internal-scope name resolution.

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-14445?

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-14445 is a malicious package: digitalexp-style-module-l9 (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-14445/ (Markdown: https://insights.sbomify.com/MAL-2026-14445/index.md)
```

## Sources

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

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