The quota client uses a generic active-provider key but sends it to hard-coded GLM quota hosts, while its host selection does not reject other providers. Because this flow serves the package’s quota feature but can expose unrelated provider credentials, classify it as a credential leak vulnerability rather than intentional theft.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A Martty session starts the quota refresher; it runs immediately and periodically while active.
Impact
The GLM endpoint receives credentials belonging to another configured provider, potentially exposing that provider account to misuse.
Mechanism
The quota client loads the active provider’s generic API key and sends it as a Bearer token. Provider URLs other than api.z.ai resolve to open.bigmodel.cn.
Evidence
dist/backend/credentials.jsdist/quota/client.jsdist/handlers/session.jsdist/quota/live.js~/.zcode/v2/config.json