Automation Workflows 0.1.0

Security checks across malware telemetry and agentic risk

Overview

This is a plain educational automation guide with no executable code or hidden account access.

Before following the guide, review what each automation can read or change, use the narrowest account permissions available, test with sample or sandbox data, and avoid enabling workflows that contact customers, move payment data, or update business records until the mappings and rollback plan are verified.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (2)

Vague Triggers

Medium
Confidence
89% confidence
Finding
The trigger phrases are broad enough to match common conversational language such as 'save time' or 'automation', which can cause the skill to activate in contexts where the user did not explicitly request workflow design. Over-broad activation increases the chance of unintended guidance for integrations, data movement, or automations affecting external systems without sufficiently scoped user intent.

Missing User Warnings

Medium
Confidence
91% confidence
Finding
The skill encourages automations involving CRMs, spreadsheets, email tools, Slack, payment systems, and customer data, but the description does not warn users about privacy, consent, or the risks of automated data transfer and actions. Without explicit cautions, users may deploy workflows that expose personal or financial data, trigger unauthorized communications, or make business-impacting changes without adequate review.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal