The flagged credential flows serve the configured Slack and Jira integrations, and the persistence code is reached through an explicit PR watch install action. The manifest declares no install lifecycle hook or automatic install-time activity.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Slack posting and PR watch scheduling require an explicit function or command; Jira verification is part of machine setup.
Impact
Expected integration and scheduling behavior; no evidence of unrelated credential collection, hidden persistence, or automatic account actions.
Mechanism
Configured Slack credentials go to Slack, Jira credentials go to the configured Jira base URL, and scheduling creates a PR watch launch agent or crontab entry when explicitly requested.
Evidence
dist/sandbox.jsdist/machine_setup.js
Network endpoints2
slack.comuser-configured Jira base_url