The Anthropic credential is disclosed to a different service, potentially exposing the associated account or API usage.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The reader automatically uses an Anthropic credential as the authorization token for a DeepSeek request. This is cross-service credential disclosure and warrants blocking the package.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A running local reader receives a POST to /api/explain while ANTHROPIC_AUTH_TOKEN is set in the CLI process environment.
Mechanism
The Python handler selects ANTHROPIC_AUTH_TOKEN before DEEPSEEK_API_KEY and attaches the selected value as a Bearer token to a DeepSeek API request.
Attack narrative
When the local reader handles an explanation request, it reads ANTHROPIC_AUTH_TOKEN before checking for a DeepSeek key, then sends that value as a Bearer credential to api.deepseek.com. The Python child inherits the CLI process environment, making the cross-service credential available to this handler.
Avoid installing weflow-cli@1.8.2. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.