magpie-opc-auth@0.1.2
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-aiSuccessful login automatically triggers eligible daily tasks, including public posting to a hard-coded community circle with the user's account. This is an unrequested account action toward a publisher-selected target, so the package should be blocked.
Decision evidence
public snapshot- Successful browser login automatically starts background daily tasks using the account cookie.
- With no task filter configured, the task runner considers all tasks returned by the service.
- The plaza task publishes generated content to a hard-coded check-in circle through an authenticated POST.
- The package describes itself as a FiimeOPC provider with daily check-in functionality.
- The manifest declares no install lifecycle scripts.
- The plugin’s normal model and account requests target FiimeOPC, its stated service.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
scripts/check.mjsView on unpkg · L174Package ships non-JavaScript build or shell helper files.
extract-contract.pyView on unpkgFindings
Affected versions and remediation
This report applies to magpie-opc-auth@0.1.2.
See all versions of magpie-opc-auth for other recorded verdicts.
- Avoid installing magpie-opc-auth@0.1.2. 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.