scrollcraft

SUSPICIOUS. The core build, file access, and local verification steps are broadly consistent with a scroll-page design skill, and the npm/Playwright usage is normal developer tooling. The main concern is the optional kie.ai integration: it sends prompts, assets, and a paid API credential through a third-party gateway rather than official model-provider APIs, which is a real data-flow and trust expansion not strictly necessary for the stated purpose. Overall this looks more like a legitimate but higher-risk creative workflow skill than a malicious credential harvester.

No overt malicious/backdoor behavior is evident in the provided file (no eval/exec, no persistence, no stealthy activity). However, the module implements an explicit local-file upload (base64 exfiltration) capability to a hardcoded third-party endpoint whenever local paths are supplied, and it performs unvalidated downloading from API-returned URLs and arbitrary file writes to a user-provided output path. The security posture is therefore dominated by data-exfiltration and operational misuse risk rather than by clear malware. Careful trust-model review and input/output validation (file allowlists/size limits, URL allowlisting, safer output path handling) are recommended for supply-chain scenarios.