ClawHub
Back to skill

Security audit

Gpu Check

Security checks for vulnerabilities and agentic risk

Overview

This is a narrow GPU status checker that queries two disclosed local-network GPU endpoints, with dependency hygiene issues users should review before installing.

Install this only if you expect the skill to contact 192.168.2.236:5000/gpu and 192.168.2.164:5000/gpu on your local network. Before use, update or audit the npm dependencies, especially axios and its transitive HTTP packages, and consider adding English or locale-aware documentation if the skill will be shared outside a Chinese-speaking environment.

A.I.G

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (9)

Known Vulnerable Dependency: axios==1.13.5 — 16 advisory(ies): CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +13 more

High
Category
Supply Chain
Confidence
94% confidence
Finding
The lockfile pins axios 1.13.5, and the finding cites multiple known advisories including SSRF/proxy bypass and prototype-pollution-related MITM/credential theft issues. Even though a lockfile alone does not prove the vulnerable code paths are exercised, shipping a known vulnerable HTTP client dependency is a real supply-chain risk because any future or existing network-facing usage in the skill could inherit those flaws.

Known Vulnerable Dependency: form-data==4.0.5 — 1 advisory(ies): CVE-2026-12143 (form-data: CRLF injection in form-data via unescaped multipart field names and f)

High
Category
Supply Chain
Confidence
89% confidence
Finding
form-data 4.0.5 is reported vulnerable to CRLF injection through unescaped multipart field names/filenames. If any part of a multipart request is built from attacker-controlled input, this can lead to malformed requests, header injection, or request smuggling-style effects against downstream services.

Known Vulnerable Dependency: axios==1.13.5 — 16 advisory(ies): CVE-2026-44494 (axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `co); CVE-2026-44495 (axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollut); CVE-2025-62718 (Axios has a NO_PROXY Hostname Normalization Bypass that Leads to SSRF) +13 more

High
Category
Supply Chain
Confidence
98% confidence
Finding
The package explicitly depends on axios 1.13.5, which the finding indicates has multiple published security advisories, including SSRF-related and prototype-pollution-adjacent issues. If this skill uses axios for network access, these flaws could enable request manipulation, credential leakage, response hijacking, or other network-originated compromise depending on how the library is used.

Natural-Language Policy Violations

Medium
Confidence
90% confidence
Finding
The entire skill description and example invocations are presented only in Chinese, including the required chat phrases. This imposes a specific language/locale on users without documenting an option to use another language or explaining a justified region-specific constraint.

Natural-Language Policy Violations

Medium
Confidence
96% confidence
Finding
The strings returned to users at L21 and L23 are written in Chinese, which forces a specific language for status messages. This is a natural-language policy concern because the file provides no opt-in, fallback, or explanation that the skill is intentionally limited to a Chinese-speaking audience.

Natural-Language Policy Violations

Medium
Confidence
91% confidence
Finding
The skill includes comments and returned status messages only in Chinese, with no mechanism to let the user choose or confirm the language. Per the policy criteria, forcing a specific language without opt-in is a natural-language policy violation.

Missing User Warnings

Low
Confidence
83% confidence
Finding
This code sends a network request to configured internal node addresses, which is a safety-relevant operation under the code-file warning criteria. The file contains no docstring, comment, print/log statement, or confirmation explaining that running the skill will contact remote systems.

Known Vulnerable Dependency: follow-redirects==1.15.11 — 1 advisory(ies): CVE-2026-40895 (follow-redirects leaks Custom Authentication Headers to Cross-Domain Redirect Ta)

Low
Category
Supply Chain
Confidence
88% confidence
Finding
follow-redirects 1.15.11 is flagged for leaking custom authentication headers across cross-domain redirects. As a transitive dependency of axios, this can expose bearer tokens or other secrets if the application follows attacker-influenced redirects, making it a genuine vulnerability when HTTP requests are performed against untrusted or partially trusted endpoints.

Unpinned Dependencies

Low
Category
Supply Chain
Content
"author": "",
  "license": "ISC",
  "dependencies": {
    "axios": "^1.13.5"
  }
}
Confidence
93% confidence
Finding
The dependency is specified with a caret range (^1.13.5), which allows installation of newer minor and patch versions outside an exact, reviewed build. This weakens supply-chain reproducibility and can unintentionally pull in changed or compromised dependency code during future installs.

Static analysis

No suspicious patterns detected.