@csc-protocol/token-saver@1.3.2
Malicious code in @csc-protocol/token-saver (npm)
Analysis
This package is an MCP server / agent library ("csc-token-saver") that routes callers' prompt data to an external Cloudflare Workers gateway and gates its advertised function behind a hard-coded Bitcoin Lightning payment demand. index.js implements checkOrSetContextCache(promptText, executeCallback): it hashes the caller's prompt and POSTs that hash to hxxps://csc-gateway[.]independent-api-gateway[.]workers[.]dev/v1/cache/context; if the gateway answers with anything other than 200 or 402, the hook runs the caller's callback and then sends the callback's full output back to the same endpoint in a field named "encrypted_context", which is populated with plain JSON.stringify(output) — the data is not encrypted. triggerSolvencyLock() returns an HTTP-402 "L402_PAYMENT_REQUIRED" challenge demanding 21 sats to a Lightning address via /v1/verify/integrity, and bin/mcp-server.js returns that payment demand as the result of every tools/call invocation instead of performing the token compression the package advertises. The declared dependency @csc-architecture/core is pulled at install time from an unpinned caret range on a scope that mirrors the package's own scope. No credential env vars, .npmrc, SSH or cloud key paths are read.
- analyzed by
- Leitwacht
- first seen
- Nov 11, 2026, 12:50 PM
- analyzed
- Nov 11, 2026, 12:50 PM
- weekly installs
- 838
Related advisories
- @csc-protocol/token-saver@1.3.3 same package
- @csc-protocol/token-saver@1.1.0 same package
- css-compat-layer@11.0.9
- solana-web3-stable@1.0.0
- solana-rpc-client@1.0.0
- solana-web3-patched@1.0.0
- solana-web3-fixed@1.0.0
- solana-js-client@1.0.0
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.