magpie-trustoken-auth@0.3.13
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 defaults auto-check-in on and its daily-task fallback makes model calls with the user’s API key without a per-use request. The calls target the package’s own service and are narrowly bounded, but the automatic quota use meets the rule for malicious automatic spending.
Decision evidence
public snapshot- The package enables Magpie auto-check-in by default.
- When daily-task gaps exist, the check-in hook creates AiPy tasks and, if the local task path is unavailable, falls back to direct model calls.
- That fallback sends the user’s API key to the Trustoken model gateway in chat requests, consuming account quota automatically.
- The package describes auto-check-in and daily-task rewards as features.
- The fallback prompt is limited to a short “reply OK” request with a four-token output limit.
- The API key is sent to the package’s declared Trustoken gateway, and the AiPy task path uses a loopback endpoint.
Source & flagged code
12 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.3.13.
See all versions of magpie-trustoken-auth for other recorded verdicts.
- Avoid installing magpie-trustoken-auth@0.3.13. 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.