tako-cli@0.3.47
Tako CLI — unified launcher for AI coding tools (Claude Code, Codex, Pi, Gemini, Grok Build) with multi-agent session management
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package’s stated telemetry purpose is ordinary, but its default startup telemetry sends provider email or account identifiers to the operator’s analytics service while describing the data as anonymous. This is suspicious identifying telemetry; the inspected flow did not show API credentials or prompt content being sent.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Starting the CLI, when a provider is configured and telemetry has not been disabled.
Impact
The operator receives identifying account information and usage events without the user opting in.
Mechanism
The CLI selects an account or provider identifier, attaches a configured provider email and usage metadata, then tracks it through OpenPanel at the operator’s endpoint.
AI rationale
The package’s stated telemetry purpose is ordinary, but its default startup telemetry sends provider email or account identifiers to the operator’s analytics service while describing the data as anonymous. This is suspicious identifying telemetry; the inspected flow did not show API credentials or prompt content being sent.
Evidence
dist/index.js
Network endpoints1
op.shiroha.tech/api/track
Decision evidence
public snapshotAI called this Suspicious at 97.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest exposes dist/index.js as the tako executable.
- Telemetry is enabled unless telemetryEnabled is explicitly false; the tracker uses https://op.shiroha.tech/api.
- On startup, telemetry identifies the user using an account ID or provider ID and attaches a configured provider email, along with region, locale, version and platform.
- The normal CLI startup path invokes the telemetry identity and cli_started tracking functions.
- Launch events include a hash of the project path rather than the path itself.
Evidence against
- The package is a CLI launcher for AI coding tools, and its manifest has no install lifecycle hook.
- The inspected telemetry sends account identifiers and usage metadata; no API credential or prompt content was found in that flow.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinified
Source & flagged code
15 flaggeddist/index.jsView file
2Source sends the broad process environment to a literal external destination.
L2: // @bun
L3: var GM=Object.create;var{getPrototypeOf:HM,defineProperty:Vv,getOwnPropertyNames:PM}=Object;var Xv=Object.prototype.hasOwnProperty;function zM(e){return this[e]}var KM,JM,Be=(e,o,i...
L4: `).map((a)=>a.trim().replace(/\r$/,"")).filter(Boolean);if(o!=="win32")return i[0];return i.find((a)=>a.toLowerCase().endsWith(".exe"))??i.find((a)=>a.toLowerCase().endsWith(".cmd"...
...
L266: * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
L267: */});function s_(e){let o=[];for(let[i,a]of Object.entries(e)){if(!a?.models)continue;for(let[s,u]of Object.entries(a.models)){let d=u?.limit?.context;if(typeof d!=="number"||d<=0)...
L268: `);return{update(s){if(s===a)return;if(a=s,o)i(`\r\x1B[2K
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/index.jsView on unpkg · L22// @bun
L3: var GM=Object.create;var{getPrototypeOf:HM,defineProperty:Vv,getOwnPropertyNames:PM}=Object;var Xv=Object.prototype.hasOwnProperty;function zM(e){return this[e]}var KM,JM,Be=(e,o,i...
L4: `).map((a)=>a.trim().replace(/\r$/,"")).filter(Boolean);if(o!=="win32")return i[0];return i.find((a)=>a.toLowerCase().endsWith(".exe"))??i.find((a)=>a.toLowerCase().endsWith(".cmd"...
...
L266: * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
L267: */});function s_(e){let o=[];for(let[i,a]of Object.entries(e)){if(!a?.models)continue;for(let[s,u]of Object.entries(a.models)){let d=u?.limit?.context;if(typeof d!=="number"||d<=0)...
L268: `);return{update(s){if(s===a)return;if(a=s,o)i(`\r\x1B[2K\u23F3 ${s}`);else i(`\u23F3 ${s}
...
L290:
L291: `).trim()}function GS(e,o){
Findings
4 Critical10 High5 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/index.js
CriticalCredential Exfiltrationdist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
CriticalPrevious Version Dangerous Deltadist/index.js
HighChild Processdist/index.js
HighShelldist/index.js
HighSame File Env Network Executiondist/index.js
HighCredential Redirect Persistencedist/index.js
HighCommand Output Exfiltrationdist/index.js
HighSandbox Evasion Gated Capabilitydist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
High
Affected versions and remediation
This report applies to tako-cli@0.3.47.
See all versions of tako-cli for other recorded verdicts.
- Review the evidence and your use of tako-cli@0.3.47 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.