Phy Dotenv Inheritance Mapper

Security checks across malware telemetry and agentic risk

Overview

This is a local dotenv analysis skill, with the main risk that its reports may reveal secrets from .env files.

Install only if you are comfortable letting the agent read .env files in the target project. Treat the generated report as sensitive, ask for secret values to be redacted by default, and review any suggested git or .gitignore commands before running them.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Description-Behavior Mismatch

Medium
Confidence
91% confidence
Finding
The skill is presented as a read-only auditing/mapping tool, but it also includes behavior that generates replacement `.env.example` content and recommends repository-modifying commands such as `git rm --cached .env` and editing `.gitignore`. That mismatch increases the risk that an agent or user invokes the skill expecting safe inspection but is instead guided into making persistent repo changes, which is a scope-expansion and integrity risk.

Missing User Warnings

Medium
Confidence
97% confidence
Finding
The skill repeatedly instructs users to build and display a merged/effective view of `.env` values, including sample output that prints secrets like `STRIPE_SECRET_KEY` and database URLs. Because `.env` files commonly contain credentials, rendering effective values into reports can disclose secrets into chat logs, terminal scrollback, or other stored artifacts.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal