The flagged account-action location is diagnostic code that reports client identity conflicts, and I found no account action or external collector. Automatic startup work is read-only health scanning; maintenance operations require an explicit plan and confirmation.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
The host loads the plugin; a timer runs checkups after startup and on a configured schedule. User requests invoke panel actions.
Impact
No malicious impact identified; the observed behavior supports diagnostics and user-authorized maintenance.
Mechanism
The checkups read local logs and profiles. Maintenance actions require a plan hash and explicit confirmation; panel requests use the host’s advertised origin.
Evidence
DSH crash-log directories under the platform application-data paths~/.dsh/profiles/desktop~/.dsh/profiles/default~/.dsh data files for reports, settings, and audit history
Network endpoints2
same-origin /api/dsh-steward/