suspicious.dangerous_exec
- Location
- scripts/quick-analysis.mjs:15
- Finding
- Shell command execution detected (child_process).
AdvisoryAudited by Static analysis on May 10, 2026.
Detected: suspicious.dangerous_exec, suspicious.exposed_secret_literal
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If invoked with the wrong ticker, side, count, price, or order ID, the skill could create or cancel financially meaningful orders.
The script can submit and cancel Kalshi orders. This is central to the stated trading purpose, but these actions can affect real funds.
return request(creds, "POST", "/portfolio/orders", undefined, body); ... return request(creds, "DELETE", `/portfolio/orders/${encodeURIComponent(orderId)}`);Require explicit user confirmation for every buy, sell, and cancellation, including ticker, side, count, price, total cost, and order ID where applicable.
Anyone or anything able to use this configured key through the skill may be able to access account data and perform permitted Kalshi actions.
The CLI reads the user’s Kalshi private key from the configured path to sign authenticated API requests.
const pem = fs.readFileSync(keyPath, "utf-8"); const privateKey = crypto.createPrivateKey(pem);
Store the private key with restrictive permissions, use only intended Kalshi credentials, revoke the key if unsure, and consider demo credentials before live trading.
Running quick analysis executes local Node code from this skill, which is expected for the helper but should still be trusted before use.
The helper script launches the bundled CLI as a child process. The command is fixed to node and arguments are passed as an array, which limits shell-injection risk.
const proc = spawn("node", [CLI, ...args], { stdio: "pipe" });Review the bundled scripts and run them only from a trusted skill installation directory.
For a skill that can trade with real funds, unclear provenance makes it more important to inspect the code and trust the publisher.
The registry metadata does not identify a source repository or provenance for the skill.
Source: unknown
Verify the full script contents and publisher before configuring live Kalshi credentials.