ia-react-frontend

Security checks across malware telemetry and agentic risk

Overview

This React guidance skill is documentation-only and purpose-aligned; its only notable risk is an example that stores test login state on disk.

Reasonable to install. When following the Playwright auth-state example, use a dedicated non-production test account, keep e2e/.auth out of git and CI artifacts, and rotate or delete the saved state when it is no longer needed.

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

Low
Confidence
83% confidence
Finding
The example writes Playwright authentication state to `e2e/.auth/user.json`, which can persist session cookies or tokens on disk and be reused by anyone with access to the workspace, CI artifacts, or an accidentally committed file. In the context of E2E testing guidance this is a common practice, but the documentation does not mention safeguards such as using non-production accounts, gitignore protection, restricted file permissions, or cleanup, so the pattern represents a real low-severity security weakness rather than a false positive.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal