The package’s inspected credential flows target their respective provider APIs, and its MCP listener and mirror depend on explicit configuration or account wiring. The routed findings did not reveal unrelated credential transmission or other concrete attack behavior.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Provider requests occur when the model catalog is used; MCP serving requires explicit enablement, and mirror sync requires gateway and account wiring.
Impact
No unauthorized collection, account action, or destructive behavior was identified in the reviewed paths.
Mechanism
Uses provider credentials with matching provider APIs and sends configured mirror data to the FaberLoom gateway.
Network endpoints8
api.anthropic.comapi.openai.comgenerativelanguage.googleapis.comapi.deepseek.comapi.kimi.comapi.moonshot.aiharness.mwt.onesicop.vlinte.work