iblai-vibe-design

SUSPICIOUS. The skill’s capabilities mostly fit a frontend design/critique workflow, and there is no clear credential theft or unrelated data exfiltration. The main concern is install/execution trust: it relies on external CLI/binary behavior (`impeccable`) and mutable remote content, which is broader than a pure markdown skill and creates meaningful supply-chain risk, but not a fundamentally incompatible or malicious footprint.

No clear evidence of classic malware (reverse shell, cryptomining, system command execution) in this fragment. The most concerning issues are security risks: (a) dynamic script loading over HTTP from localhost, (b) fetching arbitrary https? font URLs referenced in CSS without origin/scheme allowlisting, and (c) multiple high-impact DOM XSS sinks via innerHTML using server-provided design-system data (including container.innerHTML = c.html) and unvalidated markdown link href schemes. If the localhost server or design-system payload can be influenced by an attacker, the code could execute attacker-controlled HTML/JS in the page.

This module does not show overt malware behavior (no eval/Function-based execution, no external network egress, no reverse shell/backdoor logic). However, it is security-sensitive: it provides token-gated but high-impact local file disclosure (/source), persists uploaded artifacts to disk (/annotation), and serves executable browser JavaScript assembled from local filesystem contents (/live.js) with embedded runtime authorization material. The primary risk is confidentiality compromise if the token is leaked (query-param exposure + permissive CORS), not direct malicious payload delivery from this module itself.

No definitive malware indicators (no credential theft, backdoor, persistence, or direct eval/exec of attacker-controlled code) are visible in this module. The security risk is primarily due to capability breadth: it can fetch and inline remote resources referenced by attacker-influenced DOM/CSS and can load caller-supplied Web Workers (workerUrl execution boundary). If the consuming application processes untrusted DOM/CSS or untrusted options, the module may cause unintended outbound requests and increase rendering/injection attack surface in the generated SVG/stylesheet context.