magpie-trustoken-auth@0.3.22
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 automatic check-in path can use the user’s model quota and create AiPy tasks without a separate request. The source shows this behavior is intentional, but the package rules classify automatic spending through a user’s keys as malicious.
Decision evidence
public snapshot- The package enables `autoCheckin` by default.
- The check-in hook automatically fills daily-task gaps by creating AiPy tasks.
- If the local AiPy task path is unavailable, the hook calls chat using the account API key, with a prompt and model supplied by the package.
- That chat helper sends a POST to the Trustoken model gateway, consuming the account’s model quota.
- The package reads AiPy’s local API key and uses it to force-create tasks through the local AiPy API.
- The manifest contains no install, preinstall, or postinstall lifecycle hook; its scripts are maintainer utilities.
- The model request goes to Trustoken’s own model gateway, and the AiPy API key is used against a loopback address; no foreign credential collector was identified.
- OAuth credentials are used in the package’s explicit sign-in flow with Trustoken.
Source & flagged code
13 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.22.
See all versions of magpie-trustoken-auth for other recorded verdicts.
- Avoid installing magpie-trustoken-auth@0.3.22. 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.