Source inspection shows the postinstall change is limited to FastMCP consent-screen presentation and preserves the approval controls. Credential use is directed to the configured Spidra service, with no separate malicious behavior confirmed.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
Package installation runs the postinstall hook; OAuth introspection occurs only when OAuth is configured and a session is authenticated.
Impact
No credential transfer to an unrelated recipient or consent bypass was found; the consent screen retains explicit approve and deny actions.
Mechanism
The hook replaces the consent-screen method in matching FastMCP distribution files. Runtime authentication uses the configured Spidra API, and the SDK sends its API key to the Spidra service.
Evidence
scripts/patch-fastmcp-consent.mjsdist/index.js