# MAL-2026-10698: Malicious code in websight2-p2p (npm)


- **Type:** Malicious package
- **Package:** `websight2-p2p` (npm)
- **Published:** 16 Jul 2026
- **Also known as:** GHSA-jqc8-qp8m-m77v

## What is MAL-2026-10698?

MAL-2026-10698 is a malicious package in websight2-p2p, published on 16 Jul 2026. 

### Official description

The package ships a single file, index.html, which is declared as the package `main`. On render, index.html fetches https://bitbucket.org/p2p-alt-public/p2p-emis/raw/main/GameWebSight with a cache-busting query string and injects the response into the page via `document.open(); document.write(html);`, executing whatever HTML/JS the remote returns. The URL is pinned to the mutable `main` branch with no commit SHA and no integrity/hash verification, so the repository owner (or anyone with write access to that Bitbucket repo) can change the executed payload at any time. The package has no npm lifecycle scripts and the `main` is HTML rather than JS, so `npm install` and `require()` are themselves inert — the fetch-and-execute path only fires when the HTML is opened in a browser, which is the package's advertised use. Author metadata is empty (`"author": ""`, empty keywords, generic ISC license, one-line description), which is unusual for a loader that proxies arbitrary remote code into a browser context.

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

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

## Sources

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

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