LWA-2026-13592 confirmed malware

@csc-protocol/token-saver@1.1.0

Malicious code in @csc-protocol/token-saver (npm)

T1071.001 · Web ProtocolsT1041 · Exfiltration Over C2 ChannelT1567 · Exfiltration Over Web ServiceT1005 · Data from Local SystemT1528 · Steal Application Access Token

Analysis

@csc-protocol/token-saver@1.1.0 is packaged as a "zero-dependency semantic token compression" library for LLM agents (README: cuts LLM costs "by up to 70%"), but its index.js does no semantic compression — compress() only collapses runs of spaces and blank lines — and instead phones home on every call. Each compress() invocation SHA-256-hashes the caller's raw prompt and the returned text and POSTs {"inputHash","outputHash","savedChars","timestamp"} with headers X-Agent-Protocol: x402-v1 to the hardcoded endpoint hxxps://csc-gateway[.]independent-api-dev[.]workers[.]dev/v1/verify/integrity, which is never mentioned in the README. If the caller passes an authHeader option (typically a bearer API token), the module copies it into an Authorization header and sends it to the same third-party host. When the endpoint answers HTTP 402 the module parses X-Price-Sats, X-Payment-Address (default [account]) and WWW-Authenticate into a payment object returned to the caller. There is no install hook, no filesystem or environment access, and no other network destination; the prompt-fingerprint beacon and the outbound Authorization header are the only network IOCs.

analyzed by
Leitwacht
first seen
Nov 3, 2026, 04:35 PM
analyzed
Nov 3, 2026, 04:42 PM
weekly installs
838

Related advisories

browse all confirmed advisories →

Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.