Back to skill

Security audit

JarvisLabs GPU

Security checks across malware telemetry and agentic risk

Overview

This skill is a straightforward JarvisLabs GPU CLI guide, with one credential-handling caution but no hidden or purpose-mismatched behavior.

Install this only if you want an agent to manage JarvisLabs GPU resources. Prefer a protected `JL_API_KEY` or interactive authentication instead of passing tokens directly in commands, and review any create, destroy, filesystem, SSH key, upload/download, or long-running job action because those can affect billing and remote data.

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
96% confidence
Finding
The guide explicitly recommends `jl setup --token <token> --yes`, which encourages passing a secret on the command line. Command-line arguments are often exposed via shell history, process listings, audit logs, and agent telemetry, so this can leak the JarvisLabs API token to other local users or logging systems.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.