magpie-trustoken-auth@0.3.10
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 contains explicit reviewer-directed language telling reviewers not to remove particular behavior based on review. That meets the reviewer-manipulation rule and warrants blocking this version.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A reviewer or automated agent reads AGENTS.md during package review.
Impact
Can bias reviewers into retaining behavior or discounting findings; this is explicit reviewer manipulation.
Mechanism
The file asserts that the code must be kept and explicitly says not to remove it based on review.
Attack narrative
AGENTS.md targets reviewers with an explicit instruction to preserve task creation and filler requests despite review findings. This is reviewer manipulation; the runtime account flows otherwise appear tied to the package’s stated Trustoken and AiPy features.
AI rationale
The package contains explicit reviewer-directed language telling reviewers not to remove particular behavior based on review. That meets the reviewer-manipulation rule and warrants blocking this version.
Evidence
AGENTS.md
Decision evidence
public snapshotAI called this Malicious at 97.0% confidence as Malware with low false-positive risk.
Evidence for block
- AGENTS.md explicitly tells reviewers that task creation and filler requests must be retained and says not to remove them based on review, attempting to influence the security review.
Evidence against
- The package has no lifecycle scripts; its entry point assembles plugin hooks.
- The task automation uses the account’s Trustoken credentials with Trustoken APIs and a key for the local AiPy API, consistent with the stated sign-in and daily-task features.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
11 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.8
matchedPath = scripts/score.mjs
matchedIdentity = npm:bWFncGllLXRydXN0b2tlbi1hdXRo:0.3.8
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.8
matchedPath = scripts/check.mjs
matchedIdentity = npm:bWFncGllLXRydXN0b2tlbi1hdXRo:0.3.8
similarity = 1.000
summary = normalized source hash matched finalized malicious source
Findings
11 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
HighPrevious Version Dangerous Deltasrc/hooks/methods.mjs
MediumDynamic Require
Affected versions and remediation
This report applies to magpie-trustoken-auth@0.3.10.
See all versions of magpie-trustoken-auth for other recorded verdicts.
- Avoid installing magpie-trustoken-auth@0.3.10. 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.