ClawHub
Back to skill

Security audit

Claude Code MiniMax 配置

Security checks across malware telemetry and agentic risk

Overview

This is a coherent setup guide for using Claude Code with MiniMax, but users should handle the MiniMax API key carefully.

Install only if you are comfortable routing Claude Code traffic to MiniMax and storing a MiniMax API key locally. Use a dedicated/limited key if possible, do not commit config files containing secrets, review cc-switch before installing it, and only trust Claude Code folders you control.

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 (2)

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The guide instructs users to place a live API key directly into a local settings file but does not clearly warn about local secret exposure, file permission hardening, or avoiding accidental inclusion in backups, dotfile sync, screenshots, or version control. This creates a realistic risk of credential leakage even if the configuration is otherwise legitimate.

Missing User Warnings

Medium
Confidence
95% confidence
Finding
The troubleshooting command places a bearer token directly on the command line, which may be captured in shell history, process listings, terminal logs, or remote session recordings. This unnecessarily increases the chance of credential disclosure during debugging.

VirusTotal

62/62 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.