registry / @stacksjs/actions / 0.75.399
@stacksjs/actions@0.75.399
The Stacks actions.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package does not show an automatic attack, but its exported SSL setup helper interpolates a caller-controlled domain into a sudo shell command. That creates a real privileged command injection risk when setup is explicitly run with an untrusted project value.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
A user explicitly invokes SSL setup with an attacker-controlled domain from options.domain or APP_URL and approves the sudo operation.
Impact
The injected command could execute with elevated privileges; the helper also modifies /etc/hosts and installs local SSL certificates into trusted certificate stores.
Mechanism
The domain is interpolated into a hosts-file shell command run with sudo without shell escaping.
AI rationale
The package does not show an automatic attack, but its exported SSL setup helper interpolates a caller-controlled domain into a sudo shell command. That creates a real privileged command injection risk when setup is explicitly run with an untrusted project value.
Evidence
dist/setup/ssl.js/etc/hosts/usr/local/share/ca-certificates/stacks/Library/Keychains/System.keychain~/.stacks/ssl
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The SSL helper inserts the selected domain into a shell command that runs through sudo, without shell escaping.
- The helper accepts `options.domain` or `APP_URL`, so an attacker-controlled project value can reach that privileged command when a user explicitly runs SSL setup.
- Deployment code reads AWS credentials for its AWS deployment flow and uses AWS STS to retrieve the account identity; no unrelated credential collector was identified.
Evidence against
- The only lifecycle script is `prepublishOnly`, which runs the package build.
- SSL setup is exposed as a helper and requires an explicit setup call; the package entry point does not invoke it automatically.
- The reported `stacksjs.com` match in deployment is in subscriber email content, while AWS credentials are used in the AWS deployment flow.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
Source & flagged code
16 flaggeddist/github-release.jsView file
5patternName = generic_password
severity = medium
line = 5
Medium
dist/lint/stx-gate.jsView file
1import{existsSync}from"node:fs";import{join}from"node:path";import process from"node:process";import{Glob}from"bun";export const DEFAULT_STX_LINT_CONFIG={stxGlob:"resources/**/*.st...
L2: `).forEach((line,i)=>{re.lastIndex=0;if(!re.test(line))return;if(ignore){ignore.lastIndex=0;if(ignore.test(line))return}hits.push(`${f}:${i+1} ${line.trim().slice(0,90)}`)})}retur...
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/lint/stx-gate.jsView on unpkg · L1dist/discover-packages.jsView file
Findings
14 High5 Medium6 Low
HighCopied Package Dependency Bridgedist/discover-packages.js
HighSemantic Analysis Limiteddist/pantry-lock.js
HighKnown Malware Source Similaritydist/setup/ssl.js
HighKnown Malware Source Similaritydist/deploy/index.js
HighKnown Malware Source Similaritydist/dev/system-tray.js
HighKnown Malware Source Similaritydist/project-scripts.js
HighKnown Malware Source Similaritydist/upgrade/framework-utils.js
HighKnown Malware Source Similaritydist/upgrade/framework.js
HighKnown Malware Source Similaritydist/dev/dashboard-supervisor.js
HighKnown Malware Source Similaritydist/make.js
HighKnown Malware Source Similarity
Affected versions and remediation
This report applies to @stacksjs/actions@0.75.399.
See all versions of @stacksjs/actions for other recorded verdicts.
- Review the evidence and your use of @stacksjs/actions@0.75.399 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.