magpie-trustoken-auth
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.
This report shows the evidence for magpie-trustoken-auth@0.4.0. 18 of 21 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package automatically uses the user's service key and quota to generate task-shaped requests and claim rewards during default check-in. This is concrete unauthorized automated use of the user's account resources, so the package should be blocked.
Decision evidence
public snapshot- The package enables Magpie auto-check-in by default and exposes the check-in hook.
- When daily task gaps exist, check-in uses the account API key to issue repeated remote AI requests.
- Those requests send the API key as a Bearer credential to api.trustoken.cn.
- The hook automatically claims rewards for tasks marked claimable.
- The requests go to Trustoken, the service this provider serves; no unrelated credential destination was identified.
- The package describes auto-check-in and daily-task rewards as features.
Source & flagged code
11 flaggedSource file is highly similar to a previously finalized malicious package; route for source-aware review.
scripts/score.mjsView on unpkgFindings
Affected versions and remediation
This report applies to magpie-trustoken-auth@0.4.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing magpie-trustoken-auth@0.4.0. 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.