@goodandready/dsh-cron@0.3.24
Background automation runner for DSH: isolated agent runs, script/HTTP/SSH/Docker runtimes, cost guard, notifications, heartbeats.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe issue-creation path uses the user's Gitea credentials for a publisher-selected repository, and the UI's general LLM-actions toggle does not let the user choose that target. Although disabled by default and limited to a local Gitea service, this is an unrequested account action when enabled.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A successful LLM task emits a create_issue directive while llmActionsEnabled is enabled.
Impact
The package can use the user's Gitea credentials to post issues to the publisher's repository without the user selecting that target.
Mechanism
The helper reads GITEA_TOKEN or a token from GITEA_CREDENTIALS_PATH, then sends it in an Authorization header to the local Gitea API. The repository defaults to goodandready/dsh-cron.
Attack narrative
When structured LLM actions are enabled, successful task output can request issue creation. The package reads a local Gitea token and posts an issue to goodandready/dsh-cron, a repository hard-coded by the publisher rather than selected by the user.
AI rationale
The issue-creation path uses the user's Gitea credentials for a publisher-selected repository, and the UI's general LLM-actions toggle does not let the user choose that target. Although disabled by default and limited to a local Gitea service, this is an unrequested account action when enabled.
Evidence
lib/llm-actions.jslib/scheduler-completion.jslib/settings.jslib/client.jsPath specified by GITEA_CREDENTIALS_PATH (read)
Network endpoints1
127.0.0.1:3005/api/v1/repos/goodandready/dsh-cron/issues
Decision evidence
public snapshotAI called this Malicious at 91.0% confidence as Malware with low false-positive risk.
Evidence for block
- The issue helper defaults to the publisher's repository, goodandready/dsh-cron, and reads GITEA_TOKEN or a token from the configured credentials file.
- It uses that token to POST an issue to the local Gitea API for the selected repository.
- Successful LLM task output can trigger structured actions when llmActionsEnabled is enabled; create_issue calls the issue helper.
- The setting is exposed as a UI option for enabling structured LLM actions, including issue creation.
Evidence against
- LLM actions are disabled by default.
- The token is sent to a localhost Gitea endpoint, not an unrelated external host.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedlib/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...',
...
L254: 'form.preflightLabel': 'Pre-flight check', 'form.preflightNone': 'None',
L255: 'form.preflightHttp': 'HTTP (2xx probe)', 'form.preflightShell': 'Shell command (exit code 0)',
L256: 'form.preflightDisk': 'Disk space (path:minPercent)',
...
L778: try {
L779: data = await res.json();
L780: } catch (jsonErr) {
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
lib/client.jsView on unpkg · L128128Trigger-reachable chain: manifest.exports -> lib/client.js
L128: '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...',
...
L254: 'form.preflightLabel': 'Pre-flight check', 'form.preflightNone': 'None',
L255: 'form.preflightHttp': 'HTTP (2xx probe)', 'form.preflightShell': 'Shell command (exit code 0)',
L256: 'form.preflightDisk': 'Disk space (path:minPercent)',
...
L778: try {
L779: data = await res.json();
Findings
2 Critical3 High3 Medium4 Low
CriticalCredential Exfiltrationlib/client.js
CriticalTrigger Reachable Dangerous Capabilitylib/client.js
HighTrigger Reachable Credential Exfiltrationlib/client.js
HighSemantic Analysis Limitedcordis.patch.yml
HighAi Review Evidencelib/llm-actions.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @goodandready/dsh-cron@0.3.24.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Avoid installing @goodandready/dsh-cron@0.3.24. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.