The worker automatically captures issue titles and request or comment text and sends it through the Supermemory save path, despite the README saying it does not save automatically. Because this captures task content without a per-content request, classify it as suspicious runtime collection rather than a credential theft or malware block.
Static reason
One or more suspicious static signals were detected.
Trigger
When the plugin is running, issue.created and issue.comment.created events from non-agent actors trigger capture for an assigned agent.
Impact
Task or comment content may be retained in a memory namespace without a save request for that specific content. The package describes automatic recording after runs, but its README says it does not save automatically and does not describe this issue-event capture.
Mechanism
The worker constructs content from the issue title and up to 600 characters of the event body or description, then sends it through the Supermemory save path. Depending on settings, it may go directly to approved memory or to candidate staging.
Evidence
dist/worker.jsREADME.mddist/manifest.js
Network endpoints1
otomatik.tail77a9ab.ts.net:18443