@goodandready/dsh-cron@0.3.33
Background automation runner for DSH: isolated agent runs, script/HTTP/SSH/Docker runtimes, cost guard, notifications, heartbeats.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package has no install-time attack behavior, and the flagged SSH reference is only a key-path input. However, enabled LLM actions can use a local Gitea token to create issues in a hard-coded publisher repository, creating an account-action risk despite the global opt-in.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
A successful LLM task emits a `create_issue` directive while LLM actions are enabled and a local Gitea token is available.
Impact
Could create an issue in the publisher-selected repository using the user's local Gitea account without selecting that destination for the task.
Mechanism
The helper reads a local Gitea token and sends it with an issue creation request to `127.0.0.1:3005`; the repository defaults to `goodandready/dsh-cron`.
AI rationale
The package has no install-time attack behavior, and the flagged SSH reference is only a key-path input. However, enabled LLM actions can use a local Gitea token to create issues in a hard-coded publisher repository, creating an account-action risk despite the global opt-in.
Evidence
lib/scheduler/scheduler-completion.jslib/llm-actions.jslib/settings.js
Network endpoints1
127.0.0.1:3005/api/v1/repos/${repo}/issues
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- After a successful LLM task, output directives can run when the global LLM-actions setting is enabled.
- A `create_issue` directive uses a helper whose default repository is `goodandready/dsh-cron`.
- The helper reads `GITEA_TOKEN` or a token from the path in `GITEA_CREDENTIALS_PATH`, then posts it to the local Gitea issue endpoint.
Evidence against
- LLM actions are disabled by default, and the settings UI labels the option as enabling task triggers, notifications, and issue creation.
- The request targets loopback at `127.0.0.1:3005`; the inspected source does not show credentials sent to an unrelated external host.
- The manifest has no install lifecycle scripts, and the SSH-key routing hint points to a UI field for a user-supplied key path.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
11 flaggedlib/tui-settings.jsView file
68label: 'Feishu Webhook URL',
L69: placeholder: 'https://open.feishu.cn/open-apis/bot/v2/hook/...',
L70: format: textFormat,
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
lib/tui-settings.jsView on unpkg · L68lib/client.jsView file
128'form.sshTargetLabel': 'Fallback target (user@host, optional)',
L129: 'form.sshKeyLabel': 'Private key path (fallback, optional)',
L130: 'form.dockerImageLabel': 'Container image', 'form.sk[redacted]': 'Skill name',
...
L155: 'form.promptLabelLlm': 'Instruction / Prompt for the agent',
L156: 'form.promptPlaceholderScript': 'curl -fsSL https://... || exit 1',
L157: 'form.promptPlaceholderLlm': 'Describe exactly what the agent should do...',
...
L255: 'form.preflightLabel': 'Pre-flight check', 'form.preflightNone': 'None',
L256: 'form.preflightHttp': 'HTTP (2xx probe)', 'form.preflightShell': 'Shell command (exit code 0)',
L257: 'form.preflightDisk': 'Disk space (path:minPercent)',
...
L817: try {
L818: data = await res.json();
L819: } catch (jsonErr) {
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
Findings
3 Critical8 High3 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationlib/tui-settings.js
CriticalCredential Exfiltrationlib/client.js
CriticalTrigger Reachable Dangerous Capabilitylib/client.js
HighTrigger Reachable Credential Exfiltrationlib/client.js
HighSemantic Analysis Limitedcordis.patch.yml
HighKnown Malware Source Similaritylib/runtimes/runner-external.js
HighKnown Malware Source Similaritylib/updater.js
HighKnown Malware Source Similaritylib/llm-actions.js
HighKnown Malware Source Similaritylib/scheduler/scheduler-preflight.js
HighKnown Malware Source Similaritylib/secrets.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to @goodandready/dsh-cron@0.3.33.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Review the evidence and your use of @goodandready/dsh-cron@0.3.33 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.