magpie-trustoken-auth@0.3.8
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 check-in path can spend the user's model quota by creating tasks or sending fallback chat requests to advance reward progress. This automatic account-backed usage is a concrete risk even though the package describes its check-in purpose and the local key flow remains on loopback.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Magpie invokes the check-in hook while autoCheckin is enabled; incomplete daily-task progress triggers task creation or fallback chat requests.
Impact
Unrequested model usage can consume the user's quota or incur costs.
Mechanism
The hook uses AiPy's local API key to create model tasks, or sends short chat requests with the account API key when local task creation is unavailable.
Attack narrative
With autoCheckin enabled by default, incomplete reward tasks can cause the plugin to create AiPy model tasks or, if that fails, send chat requests using the account API key. This can consume the user's model quota without a separate request for that usage.
AI rationale
The default check-in path can spend the user's model quota by creating tasks or sending fallback chat requests to advance reward progress. This automatic account-backed usage is a concrete risk even though the package describes its check-in purpose and the local key flow remains on loopback.
Evidence
package.jsonsrc/hooks/checkin.mjssrc/aipy-local.mjssrc/api.mjs
Network endpoints2
127.0.0.1:<port>/api/aipy/createTaskapi.trustoken.cn/v1/chat/completions
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- Package metadata enables autoCheckin by default.
- The check-in hook creates AiPy tasks when daily-task progress is incomplete.
- If local task creation fails, the hook sends chat requests using the account API key.
- Task creation reads AiPy's local API key and authenticates to a loopback endpoint.
Evidence against
- The package describes itself as providing automatic check-in and daily-task rewards.
- The local AiPy API key is sent to 127.0.0.1, not an external host.
- The fallback request uses the cheapest model and requests at most four tokens.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
9 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.6
matchedPath = scripts/score.mjs
matchedIdentity = npm:bWFncGllLXRydXN0b2tlbi1hdXRo:0.3.6
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.6
matchedPath = scripts/check.mjs
matchedIdentity = npm:bWFncGllLXRydXN0b2tlbi1hdXRo:0.3.6
similarity = 1.000
summary = normalized source hash matched finalized malicious source
Findings
9 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 Similarityscripts/release.mjs
HighKnown Malware Source Similarityscripts/check-magpie-stable.mjs
HighKnown Malware Source Similarityscripts/check.mjs
HighKnown Malware Source Similarityscripts/score.mjs
MediumDynamic Requirescripts/check.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to magpie-trustoken-auth@0.3.8.
See all versions of magpie-trustoken-auth for other recorded verdicts.
- Avoid installing magpie-trustoken-auth@0.3.8. 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.