magpie-trustoken-auth@0.3.19
Trustoken / AiPy for magpie — phone-code sign-in, the account's live model list, 灵石 balance, auto check-in and daily-task rewards. DeepSeek / Qwen / GLM / Doubao / Kimi / Hunyuan.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s default auto-check-in path can issue model requests using the user’s API key to pursue daily-task rewards, including a direct fallback to the Trustoken model gateway. This is an automatic use of credentials that can consume account quota or credits, so it meets the stated rule for malicious automatic spending.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Magpie’s default auto-check-in invokes the check-in hook when daily-task gaps exist; the model-call fallback runs if local AiPy task creation is unavailable.
Impact
Unrequested model calls can consume the user’s account quota or credits. The source limits the prompts to short task-completion requests.
Mechanism
The fallback sends minimal prompts with the stored API key to Trustoken’s model chat endpoint. The primary task path also reads AiPy’s local API key and creates forced tasks through localhost.
Attack narrative
With auto-check-in enabled by default, the check-in hook fills daily-task gaps. If local AiPy task creation is unavailable, it uses the stored Trustoken API key to submit model requests, which can consume the user’s quota or credits without a separate request for those calls.
AI rationale
The package’s default auto-check-in path can issue model requests using the user’s API key to pursue daily-task rewards, including a direct fallback to the Trustoken model gateway. This is an automatic use of credentials that can consume account quota or credits, so it meets the stated rule for malicious automatic spending.
Evidence
package.jsonsrc/hooks/checkin.mjssrc/api.mjssrc/aipy-local.mjs%APPDATA%\aipy-pro\aipy (SQLite opened read-only)
Network endpoints3
api.trustoken.cn/v1/chat/completions127.0.0.1:<port>/api/aipy/createTaskwww.trustoken.cn
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package enables `magpie.autoCheckin` by default.
- When local AiPy task creation is unavailable, the check-in hook sends one or more `chatOnce` requests using the account API key and a minimal prompt.
- `chatOnce` posts that key as a bearer credential to the Trustoken model gateway’s `/chat/completions` endpoint.
- The other task path reads AiPy’s local API key and uses it to create forced tasks through the local AiPy API.
Evidence against
- The package describes itself as a Trustoken/AiPy provider with auto check-in and daily-task rewards.
- The AiPy task-creation request goes to localhost; the source shows no unrelated credential collector in that flow.
- OAuth sign-in is initiated through the plugin’s explicit login method and contacts Trustoken’s own service.
- The manifest has no install lifecycle scripts. No unrelated data exfiltration was identified.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
Source & flagged code
13 flaggedscripts/score.mjsView file
15import { join, resolve } from "node:path"
L16: import { spawnSync } from "node:child_process"
L17:
High
•matchType = normalized_sha256
matchedPackage = magpie-trustoken-auth@0.3.18
matchedPath = scripts/score.mjs
matchedIdentity = npm:bWFncGllLXRydXN0b2tlbi1hdXRo:0.3.18
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
scripts/score.mjsView on unpkgscripts/check.mjsView file
•matchType = normalized_sha256
matchedPackage = magpie-trustoken-auth@0.3.18
matchedPath = scripts/check.mjs
matchedIdentity = npm:bWFncGllLXRydXN0b2tlbi1hdXRo:0.3.18
similarity = 1.000
summary = normalized source hash matched finalized malicious source
Findings
13 High4 Medium4 Low
HighChild Processscripts/score.mjs
HighShell
HighSame File Env Network Executionsrc/aipy-local.mjs
HighSandbox Evasion Gated Capabilitysrc/hooks/methods.mjs
HighKnown Malware Source Similaritysrc/aipy-local.mjs
HighKnown Malware Source Similaritysrc/browser-login.mjs
HighKnown Malware Source Similarityscripts/release.mjs
HighKnown Malware Source Similarityscripts/check-magpie-stable.mjs
HighKnown Malware Source Similarityscripts/check.mjs
HighKnown Malware Source Similarityscripts/score.mjs
HighKnown Malware Source Similaritysrc/hooks/methods.mjs
HighKnown Malware Source Fingerprint Signature
Affected versions and remediation
This report applies to magpie-trustoken-auth@0.3.19.
See all versions of magpie-trustoken-auth for other recorded verdicts.
- Avoid installing magpie-trustoken-auth@0.3.19. 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.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.