Performance Tester

Security checks across malware telemetry and agentic risk

Overview

This appears to be a performance-testing skill with expected k6 and Locust guidance, but users should only run its examples against systems they are authorized to test.

Install only if you understand that performance-test scripts can disrupt services or change data. Run them only on systems you own or have explicit permission to test, prefer staging environments, use scoped test credentials, and avoid production write endpoints unless formally approved.

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: 96% confidence
Finding: The skill provides concrete load, stress, and spike testing guidance that could be applied directly to real services, but it does not clearly restrict use to authorized systems or non-production environments. In a performance-testing skill, these actions are expected, yet without an explicit safety boundary they can facilitate accidental denial-of-service against production or third-party targets.

Missing User Warnings

Medium

Confidence: 97% confidence
Finding: The k6 and Locust examples perform authenticated requests and include state-changing operations such as login and resource creation, but the skill does not warn users to use test credentials, sandbox tokens, or non-destructive endpoints. This increases the risk of unintended writes, account misuse, test-data pollution, or disruption if the examples are run against live environments.

VirusTotal

67/67 vendors flagged this skill as clean.

View on VirusTotal