The source shows a real security weakness: the RPC guard provides no authentication, while the route exposes dispatchable operations. Automatic session repair can also rewrite user logs without an explicit repair request, though it backs up the originals; these risks warrant a warning rather than a malware block.
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 RPC route is registered when the plugin starts. Separately, session repair runs automatically about 15 seconds after startup.
Impact
A caller able to reach the host's RPC endpoint can invoke its available operations without authentication. Automatic repair can discard later session events, although the original log is backed up.
Mechanism
The RPC admission check always succeeds, and the route dispatches requests after only a confirm-field check for selected destructive operations. Startup repair scans session logs and rewrites those it identifies as corrupt, keeping the prefix before the corruption.
Evidence
src/rpc-guard.jsindex.jssrc/auto-repair.jssrc/session-repair.js$DSH_HOME/sessions/**/session.v4.jsonl.zstd$DSH_HOME/sessions/**/session.v4.jsonl.zstd.repair-*