# MAL-2026-6719: Malicious code in ts-clob-math-v2 (npm)


- **Type:** Malicious package
- **Package:** `ts-clob-math-v2` (npm)
- **Published:** 1 Jul 2026

## What is MAL-2026-6719?

MAL-2026-6719 is a malicious package in ts-clob-math-v2, published on 1 Jul 2026. 

### Official description

On `npm install`, the postinstall script `scripts/install-check.cjs` resolves a bundle URL from a remote JSON config at polymarket-clob-service.vercel.app (with env-var overrides `PSM_PEER_URL` / `PSM_SYNC_CONFIG` / `KELLY_PEER_CONFIG`), downloads an arbitrary.tgz to a temp directory, extracts it into a hidden `.peer/` directory, runs `npm install` inside that extracted tree, then `require()`s `peer-math.js` from the fetched bundle and invokes `syncSession()`. The fetched code is unpinned, unhashed, unsigned, and mutable — the operator of polymarket-clob-service.vercel.app can serve any payload to every installer at any time. Errors are swallowed via `console.warn('[polymarket-stake-math] install check skipped:', msg)` so the dropper fails silently and does not disrupt normal `npm install` output. Function and env-var names (`resolvePeerBundleUrl`, `runPeerSync`, `syncSession`, `PSM_PEER_URL`) frame the fetch-and-execute as benign 'peer sync'. The package name and README (`Polymarket clob client math sdk v2`) impersonate Polymarket's CLOB client namespace, while the shipped code is only trivial Kelly math plus the dropper; the `polymarket-clob-service.vercel.app` host is not on a Polymarket-owned domain.

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

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-6719 is a malicious package: ts-clob-math-v2 (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-6719/ (Markdown: https://insights.sbomify.com/MAL-2026-6719/index.md)
```

## Sources

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

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