magpie-opc-auth@0.1.3
magpie / OpenCode provider plugin for FiimeOPC (opc.fiime.cn): browser-cookie sign-in, Token wallet + daily quota card, daily check-in, and an OpenAI-compatible chat channel backed by the site's own API keys.
AI Security Review
scanned 4h ago · by lpm-firewall-aiThe login callback automatically runs eligible daily tasks, including public posts made with the user's cookie. The source contradicts the README's claim that it does not publish those public tasks, so this is a deceptive, unrequested account action.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Successful cookie login, when a daily task is eligible and no task filter excludes it.
Impact
Public posts can be made under the user's account without an explicit request to publish them.
Mechanism
The background login handler runs all eligible daily tasks. The plaza task posts built-in content to a hard-coded circle with the user's cookie; the README says these public tasks are left for the user to decide.
Attack narrative
After cookie login succeeds, the plugin starts daily tasks in the background. When an eligible plaza task is returned, it publishes built-in content to a fixed public circle using the user's cookie. The README explicitly says the plugin does not publish the other public tasks and leaves that decision to the user, contradicting the implementation.
AI rationale
The login callback automatically runs eligible daily tasks, including public posts made with the user's cookie. The source contradicts the README's claim that it does not publish those public tasks, so this is a deceptive, unrequested account action.
Evidence
index.mjssrc/tasks.mjssrc/api.mjssrc/context.mjsREADME.md
Network endpoints4
opc.fiime.cn/api/community/postsopc.fiime.cn/api/projectsopc.fiime.cn/api/requirementsopc.fiime.cn/api/model-service/benefits/claim
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- After successful login, the plugin runs daily tasks in the background using the account cookie.
- With no task filter, the runner checks all returned daily tasks by default.
- For an eligible plaza task, the source publishes built-in content to a fixed community circle using the account cookie.
- The README says the plugin does not publish the other daily tasks and leaves that choice to the user.
- The package describes daily check-in as a feature, but that does not disclose the automatic public posting behavior.
Evidence against
- The observed account requests target FiimeOPC, the service this plugin is designed to use.
- The package advertises daily check-in and describes some automated tasks, which partially discloses background activity.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
Source & flagged code
5 flaggedscripts/check.mjsView file
174"type 是 module",
L175: "magpie 用 import() 加载，commonjs 会失败")
L176:
Medium
Dynamic Require
Package source references dynamic require/import behavior.
scripts/check.mjsView on unpkg · L174extract-contract.pyView file
•path = extract-contract.py
kind = build_helper
sizeBytes = 1838
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
extract-contract.pyView on unpkgscripts/create.mjs#virtual:normalized:round1View file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1
Findings
3 High5 Medium4 Low
HighSemantic Analysis Limitedscripts/create.mjs#virtual:normalized:round1
HighKnown Malware Source Similarityscripts/check-magpie-stable.mjs
HighAi Review Evidenceindex.mjs
MediumDynamic Requirescripts/check.mjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperextract-contract.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to magpie-opc-auth@0.1.3.
See all versions of magpie-opc-auth for other recorded verdicts.
- Avoid installing magpie-opc-auth@0.1.3. 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.