null Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

null is an AI agent skill, created by blixvip and published at blixvip/NullMotion. ClawSecure audited null across 69 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 60/100 (Moderate). The 5 findings concentrate in Code Injection, Permissions Manifest and ReDoS, including Potentially dangerous code pattern detected: exec\( and Potentially dangerous code pattern detected: exec\(. 3 were rated high or critical severity.

Is null safe?

ClawSecure audited null and assigned a security score of 60/100 (Moderate), identifying 5 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in null?

ClawSecure identified 5 findings in null, concentrated in Code Injection, Permissions Manifest and ReDoS. 3 were rated high or critical severity. The most severe include Potentially dangerous code pattern detected: exec\( and Potentially dangerous code pattern detected: exec\(.

How was null audited?

ClawSecure ran null through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 69 files from blixvip/NullMotion.

What does a score of 60 mean?

ClawSecure assigned null a security score of 60/100, placing it in the Moderate range. This reflects 5 findings led by Code Injection that warrant review before production 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 null

ClawSecure detected 5 security findings in null, spanning Code Injection, Permissions Manifest and ReDoS.

high · Potentially dangerous code pattern detected: exec\(. Code Injection finding detected in media.js.
high · Potentially dangerous code pattern detected: exec\(. Code Injection finding detected in gsap.min.js.
high · Potentially dangerous code pattern detected: exec\(. Code Injection finding detected in director-workspace.js.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
medium · ReDoS vulnerability: Nested quantifiers (potential…. ReDoS finding detected in gsap.min.js:10.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for null

Eliminate dynamic code execution

null 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.

Fix ReDoS-prone patterns

null contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.

Pin dependencies to exact versions

Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

ai-proposal-generatorScore 65/100 user-story-splitterScore 70/100 user-story-splitterScore 70/100 md-to-docxScore 68/100 requirement-breakdownScore 58/100

Scanned on October 28, 2026. null 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