huawei-cloud-vod-collector

SUSPICIOUS. The core capture-and-report purpose is coherent, but the skill’s footprint is broader than necessary: it collects extensive dialog context, can publish that data externally, and depends on an insufficiently verified third-party AtomGit-GO helper that receives/stores credentials. The localhost login flow is proportionate, but token handling and external CLI trust make the overall skill medium-high risk rather than benign.

The code appears to implement an intended feedback-to-GitCode delivery workflow rather than malware. The main security issues are path traversal and arbitrary file modification through feedback_id, arbitrary process termination through server-stop, and possible access-token exposure because the token is placed in a URL query string. External disclosure of feedback content is expected functionality but should be treated as sensitive-data handling. The shown fragment also contains a syntax error at the final `main(` call. Review and fix path validation, use an Authorization header, restrict PID control, and verify the server binary before use.

The script is an ordinary-looking installer but has meaningful supply-chain risks. It trusts a mutable remote repository, optionally installs a prebuilt archive without any checksum, and otherwise compiles unpinned external source code. These mechanisms could deliver malicious binaries if the repository, transport, archive, or build inputs are compromised. The fragment itself contains no direct evidence of malware, credential theft, exfiltration, persistence, or destructive behavior. Use of this installer should require repository provenance, a pinned revision, independently published checksums or signatures, and archive-entry validation.

The script is an installer with no direct evidence of malware, data theft, or sabotage. It has meaningful supply-chain security weaknesses: it trusts an unpinned external repository, builds arbitrary fetched source, skips checksum verification when the checksum is absent, and extracts archives without path-safety validation. Review and pin a trusted commit or signed release, use independently authenticated checksums or signatures, and validate archive members before installation.

The configuration contains no direct malware or executable malicious behavior. It does configure collection of prompts, tool results, error context, and environment information, followed by delivery to an external GitCode repository. This creates a material potential privacy and data-exfiltration risk, especially because environment collection is enabled and custom sanitizer rules are empty. Review the implementation and repository authorization before use, and disable environment collection or external delivery unless the captured data is demonstrably sanitized and intended for that repository.