ClawHub
Back to skill

Security audit

Ainative React Sdk

Security checks across malware telemetry and agentic risk

Overview

This skill appears to be a normal AINative React SDK guide, but its example exposes a long-lived API key in browser code, which can leak credentials.

Review before installing or copying examples. Do not put AINative secret API keys in REACT_APP_ or VITE_ variables or pass them directly to browser providers; keep secrets on a backend and expose only scoped, short-lived, browser-safe tokens if the service supports them.

SkillSpector

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

Missing User Warnings

Medium
Confidence
98% confidence
Finding
The documentation instructs developers to place a long-lived API key into client-side React environment variables and pass it directly into a browser provider. In CRA/Vite, these variables are bundled into the frontend and are trivially recoverable by any user of the app, enabling unauthorized API use, account abuse, and billing/credit theft; in a React SDK skill, this context makes the issue more dangerous because consumers are likely to copy the example verbatim into production.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.