magpie-trustoken-auth@0.3.18
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 default-enabled check-in hook can spend the user's model quota to advance daily tasks, including through direct chat requests when local task creation fails. The package also applies its built-in referral code during sign-up without a separate confirmation; the quota-spending behavior meets the policy's rule for 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
The host's default-enabled auto-check-in invokes the check-in hook when daily tasks have gaps; the referral attribution occurs when the user starts phone sign-in.
Impact
Unexpected model usage can reduce the user's account quota. New accounts can be attributed to the package author's referral code without a separate confirmation.
Mechanism
The hook creates AiPy tasks for gaps, then falls back to repeated chat-completion requests authenticated with the user's API key if local task creation fails. Sign-in adds the selected invite code as the OAuth authorization URL's aff parameter.
Attack narrative
With auto-check-in enabled by default, the plugin tries to fill unfinished daily tasks by creating AiPy tasks and, if that fails, sends model requests using the user's API key. Those requests can spend account quota without a separate spending confirmation. During sign-up, it also attaches the built-in author referral code to OAuth authorization when no saved invite code is available.
AI rationale
The default-enabled check-in hook can spend the user's model quota to advance daily tasks, including through direct chat requests when local task creation fails. The package also applies its built-in referral code during sign-up without a separate confirmation; the quota-spending behavior meets the policy's rule for automatic spending.
Evidence
package.jsonsrc/hooks/checkin.mjssrc/api.mjssrc/aipy-local.mjssrc/hooks/methods.mjssrc/invite.mjssrc/oauth.mjs
Network endpoints4
api.trustoken.cn/v1/chat/completions/api/user/daily_tasks/status
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- The manifest enables auto-check-in by default and describes daily-task rewards as a package feature.
- When check-in finds unfinished daily tasks, it automatically asks the local AiPy client to create tasks using the cheapest model.
- If local task creation is unavailable, the check-in hook sends repeated chat requests with the user's API key to complete the task gap, which can consume account quota.
- Phone sign-in selects an invite code without asking for it; absent a previously saved code, the built-in author referral code is attached to the OAuth authorization URL.
Evidence against
- There are no install lifecycle scripts; the package is a provider plugin whose advertised features include auto-check-in and daily-task rewards.
- The OAuth flow sends credentials to Trustoken's own service, and task creation uses the local AiPy API. No unrelated credential collector was identified.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystem
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.17
matchedPath = scripts/score.mjs
matchedIdentity = npm:bWFncGllLXRydXN0b2tlbi1hdXRo:0.3.17
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.17
matchedPath = scripts/check.mjs
matchedIdentity = npm:bWFncGllLXRydXN0b2tlbi1hdXRo:0.3.17
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.18.
See all versions of magpie-trustoken-auth for other recorded verdicts.
- Avoid installing magpie-trustoken-auth@0.3.18. 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.