The reviewed credential flows are tied to an explicit portal login and the configured portal, with token storage handled through the local vault. Although the published files are obfuscated, the flagged loader is a response-message helper and no malicious behavior was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
User runs the CLI or starts its configured agent; the MCP server requires launcher-provided environment values.
Impact
No unrelated credential collection, concealed payload execution, or unauthorized account action was identified in the inspected flows.
Mechanism
The launcher prompts for portal credentials, stores portal tokens locally, and uses them with the configured portal. It passes portal settings and a token to its MCP child process.
Network endpoints2
PORTAL_URL/api/auth/refreshFB_PORTAL_URL/api/tools/public?toolName=…