windows-control Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

windows-control is an AI agent skill, created by Spliff7AI and published at openclaw/skills. ClawSecure audited windows-control across 26 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 45/100 (High Risk). The 5 findings concentrate in Data Exfiltration, Code Injection and Permissions Manifest, including Base64 Obfuscated Payload and Base64 Obfuscated Payload. 3 were rated high or critical severity.

Is windows-control safe?

ClawSecure audited windows-control and assigned a security score of 45/100 (High Risk), identifying 5 findings across Data Exfiltration and Code Injection. Review the findings below before installing.

What did ClawSecure find in windows-control?

ClawSecure identified 5 findings in windows-control, concentrated in Data Exfiltration, Code Injection and Permissions Manifest. 3 were rated high or critical severity. The most severe include Base64 Obfuscated Payload and Base64 Obfuscated Payload.

How was windows-control audited?

ClawSecure ran windows-control through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 26 files from openclaw/skills.

What does a score of 45 mean?

ClawSecure assigned windows-control a security score of 45/100, placing it in the High Risk range. This is driven by 5 findings led by Data Exfiltration that should be addressed before use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for windows-control

ClawSecure detected 5 security findings in windows-control, spanning Data Exfiltration, Code Injection, Permissions Manifest and Policy Violation.

critical · Base64 Obfuscated Payload. Data Exfiltration finding detected in scripts/screenshot.py:17.
critical · Base64 Obfuscated Payload. Data Exfiltration finding detected in screenshot.py:17.
high · Potentially dangerous code pattern detected: base64.*decode. Code Injection finding detected in screenshot.py.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
info · Missing License Declaration. Policy Violation finding detected in SKILL.md.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for windows-control

Audit external network connections

windows-control sends data to external endpoints. Confirm each destination is expected and authorized, and remove any callback that exfiltrates data. ClawSecure monitors for known exfiltration and C2 endpoints.

Eliminate dynamic code execution

windows-control evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.

Add a config.json permissions manifest

A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.

Resolve policy violations

windows-control trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.

Related Security Research

ClawHavoc Explained: The Malware Family Targeting AI Agents→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→Why Generic Scanners Fail at AI Agent Security→

Related AI Agent Security Audits

agent-builderScore 35/100 agent-builderScore 35/100 agent-builderScore 35/100 agent-builderScore 35/100 agent-builderScore 35/100

Scanned on February 23, 2026. windows-control is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan