insta

SUSPICIOUS. The skill is largely coherent with its stated purpose as an infrastructure-management skill, and its data flows point to official InstaCloud endpoints rather than unrelated third parties. However, it combines broad cloud-mutating capability, sensitive secret access, MCP/client registration, and official-but-unpinned remote installers (`curl|sh`, `npx @latest`, auto-update), so the overall security risk is medium even without evidence of confirmed malicious intent.

This is operational documentation, not executable source, and it does not itself demonstrate malware or data theft. It contains significant supply-chain and operational security risks: curl-piped shell installers, unpinned npx latest execution, automatic updates, repository hook/skill installation, and commands that expose credentials. Verify installer provenance, pin and verify versions or checksums, review generated hooks and skills, and avoid command-line passwords. The fragment alone is insufficient to determine whether the referenced CLI or remote scripts are malicious.

The fragment is documentation for a cloud deployment and agent-integration CLI, not executable malware code. It documents several high-impact supply-chain and trust-boundary operations: remote shell installation, global npm self-installation/updates, global skill installation, remote MCP registration, secret handling, and optional audit synchronization. These warrant implementation and endpoint verification, but the provided text contains no direct evidence of malicious intent, credential theft, or sabotage. Missing implementation code prevents confirming how safely these documented operations are performed.

No malicious code is present in the supplied documentation. It describes a powerful remote infrastructure-control integration with legitimate-looking authentication and governance constraints. Security risk is elevated because the integration can execute commands and perform destructive cloud operations, and because the staging setup includes an unverified curl-piped shell installer. Verify the service origin, review tool permissions, pin or verify installer integrity, and use least-privilege credentials before deployment.