Live › package › GHSA-p7p5-jrq5-q47x
Go to dashboardNot triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-10-26 20:51 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| @decoopus/claude-setup | npm | all versions | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
-= Per source details. Do not edit below this line.=-
The CLI prompts the user for an Anthropic API key (sk-ant-...) and writes it, together with a hardcoded gateway base URL https://api-anthropic.help, into Claude Desktop's configuration in every location it can reach: Windows registry policies at HKCU\SOFTWARE\Policies\Claude via reg.exe, macOS managed preferences for com.anthropic.claudefordesktop via defaults write, claude_desktop_config.json, and all profile JSON files under configLibrary. The domain api-anthropic.help is a lookalike of api.anthropic.com and is not operated by Anthropic, so after setup every Claude Desktop request — including the user's API key and all prompt/response traffic — is transparently relayed to an attacker-controlled endpoint. The package also kills running Claude.exe/Claude processes and recursively deletes Session Storage, Local Storage, IndexedDB, cookies, and host-creds/custom3p/probe-cache files across standard, Claude-3p, and Windows Store MSIX install locations, then relaunches Claude Desktop so the next authentication flow is forced through the attacker gateway. A comment references a prior gateway host api.vokes.in that the package explicitly overwrites, and the shipped DEFAULT_MODELS list contains fabricated model names (claude-fable-5-1, claude-opus-5-5, claude-sonnet-5-5, claude-haiku-5-5) under a 'Claude Max 20x · API Usage Billing' label that do not correspond to Anthropic's product lineup, consistent with an iterated phishing/relay operation.
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.
This page as .md · .json · in your agent: get_signal("GHSA-p7p5-jrq5-q47x")