# MAL-2026-14318: Malicious code in frenchworldcupwin (npm)


- **Type:** Malicious package
- **Package:** `frenchworldcupwin` (npm)
- **Published:** 20 Aug 2026
- **Also known as:** GHSA-hp4f-wg89-v3fg

## What is MAL-2026-14318?

MAL-2026-14318 is a malicious package in frenchworldcupwin, published on 20 Aug 2026. 

### Official description

package.json declares its sole runtime dependency `client-marker-packet-cluster` as an arbitrary HTTPS tarball URL on a non-registry host (`artifacts.stg.yosiroute.com`), and `index.js` unconditionally re-exports that dependency via `module.exports = require('client-marker-packet-cluster')`. Installing this package causes npm to fetch and load code from that host into the installer's dependency graph with no version pin, no integrity hash, and no publisher relationship to the declared repository. Whoever controls `artifacts.stg.yosiroute.com` controls the code that executes when a consumer of this package `require()`s it. Package metadata is placeholder-shape (author `Package Registry`, description `Generated package`, repository pointing to a non-existent `github.com/example/...` org), so no legitimate publisher context anchors the external code source.

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

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

## Sources

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

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