ClawHub

Dialogflow Cx Conversations

Security checks across malware telemetry and agentic risk

Overview

This is a straightforward Dialogflow CX helper, but users should be careful not to send sensitive data or run tests against production unintentionally.

Install only if you intend to use Google Dialogflow CX. Use least-privilege Google Cloud credentials, prefer test or staging agents, avoid real customer audio, secrets, regulated data, or precise location data in examples, and be deliberate before running test cases against a production environment.

SkillSpector

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

Missing User Warnings

Medium
Confidence
90% confidence
Finding
The reference explicitly shows sending geoLocation, payload, parameters, and session entity data to detectIntent without any caution that these fields can contain sensitive personal or business data. In a skill intended to manage live conversations, this omission can lead users to transmit unnecessary sensitive information to a third-party service or logs without informed handling.

Missing User Warnings

Medium
Confidence
87% confidence
Finding
The audio and streaming examples document transmitting base64 audio and real-time streaming input but do not warn that voice content may include personal, biometric, or otherwise sensitive information. In a conversation-testing skill, users may treat the examples as routine and unintentionally send sensitive recordings to the remote API.

Missing User Warnings

Medium
Confidence
92% confidence
Finding
The batchRun example explicitly targets a production environment without caution that test execution may hit live integrations, mutate conversation state, trigger webhooks, or expose/consume production data. In this skill context, documenting production testing as a normal workflow increases the chance of accidental impact on live systems.

VirusTotal

66/66 vendors flagged this skill as clean.

View on VirusTotal