@swirls/cli@0.1.137
Swirls command line application
AI Security Review
scanned 25d ago · by lpm-firewall-aiThis is an automatic remote-code execution path during global installation, but the inspected package does not establish that the remote content is malicious or that it steals data. It warrants a warning for dangerous capability rather than a block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; source fingerprint signature matched known malicious package; routed for review
Trigger
Installing @swirls/cli globally with npm or Bun, outside CI and Windows.
Impact
The remote server can cause arbitrary shell commands to run with the installing user's permissions; no confirmed malicious payload was available locally.
Mechanism
The postinstall script invokes curl for https://swirls.ai/install and pipes its response to bash.
AI rationale
This is an automatic remote-code execution path during global installation, but the inspected package does not establish that the remote content is malicious or that it steals data. It warrants a warning for dangerous capability rather than a block.
Evidence
package.jsonscripts/install.jsbin/swirls
Network endpoints1
swirls.ai/install
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The package declares a postinstall hook that runs scripts/install.js.
- The hook activates for global npm or Bun installations and otherwise exits.
- When activated, it streams code from swirls.ai directly into bash with shell execution.
Evidence against
- The hook exits in CI, on Windows, and for non-global installs.
- The inspected source contains no credential collection, endpoint configuration, or data-upload logic.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
UrlStrings
NoLicense
Source & flagged code
10 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgscripts/install.jsView file
13L14: import { execSync } from 'node:child_process'
L15: import { chmodSync, copyFileSync, existsSync } from 'node:fs'
...
L18:
L19: const INSTALL_URL = 'https://swirls.ai/install'
L20:
...
L28: const INSTALLED_BINARY = join(
L29: process.env.HOME || process.env.USERPROFILE || '',
L30: '.local',
...
L36:
L37: if (process.env.CI === 'true' || process.env.CI === '1') {
L38: process.exit(0)
Critical
Download Execute
Source downloads or fetches remote code and executes it.
Findings
2 Critical7 High3 Medium4 Low
CriticalDownload Executescripts/install.js
CriticalTrigger Reachable Dangerous Capabilityscripts/install.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processscripts/install.js
HighShellscripts/install.js
HighSandbox Evasion Gated Capabilityscripts/install.js
HighSemantic Analysis Limitedbin/swirls
HighKnown Malware Source Similarityscripts/install.js
HighKnown Malware Source Fingerprint Signaturescripts/install.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @swirls/cli@0.1.137.
See all versions of @swirls/cli for other recorded verdicts.
- Review the evidence and your use of @swirls/cli@0.1.137 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.