@goodandready/dsh-cron@0.3.30
Background automation runner for DSH: isolated agent runs, script/HTTP/SSH/Docker runtimes, cost guard, notifications, heartbeats.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe issue action uses a user's Gitea token to post to the publisher's hardcoded repository, a destination the user does not configure. Although the action is opt-in and issue creation is disclosed generally, the fixed target is hidden and the user may enable the feature for other actions.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
A successful LLM task outputs a create_issue directive while llmActionsEnabled is true and a Gitea token is available.
Impact
The user's Gitea credentials can be used to post an issue to a repository selected by the publisher, without the user selecting that destination.
Mechanism
The package reads GITEA_TOKEN or a token from GITEA_CREDENTIALS_PATH, then sends an authenticated POST to the local Gitea API. The repository defaults to goodandready/dsh-cron.
Attack narrative
With structured LLM actions enabled, a successful LLM task can emit a create_issue directive. The package obtains a Gitea token from the environment or a configured credentials file and uses it to create an issue in goodandready/dsh-cron through the local Gitea API. The settings UI mentions issue creation but does not disclose this fixed repository destination.
AI rationale
The issue action uses a user's Gitea token to post to the publisher's hardcoded repository, a destination the user does not configure. Although the action is opt-in and issue creation is disclosed generally, the fixed target is hidden and the user may enable the feature for other actions.
Evidence
lib/scheduler/scheduler-completion.jslib/llm-actions.jslib/settings.jslib/client-src/70-settings-card.jsPath configured by GITEA_CREDENTIALS_PATH, if set
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
- After a successful LLM task, structured actions are processed only when llmActionsEnabled is true.
- The create_issue action reads GITEA_TOKEN or a token from the file named by GITEA_CREDENTIALS_PATH.
- The create_issue action defaults to the publisher's goodandready/dsh-cron repository.
- It sends an authenticated POST request to the local Gitea API to create the issue.
Evidence against
- LLM actions are disabled by default.
- The settings UI discloses that enabling structured LLM actions can create issues.
- The manifest declares no install, preinstall, or postinstall hook.
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)',
...
L791: try {
L792: data = await res.json();
L793: } 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.30.
See all versions of @goodandready/dsh-cron for other recorded verdicts.
- Avoid installing @goodandready/dsh-cron@0.3.30. 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.