Back to skill

Security audit

daily-standup

Security checks for vulnerabilities and agentic risk

Overview

This standup skill does what it says, but users should be aware that team updates may be reposted and stored in memory files.

Before installing, configure the exact members and channels, tell participants that submitted updates may be reposted and archived, and avoid including credentials, private HR details, customer secrets, or other sensitive information unless your team has approved retention and deletion practices.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The skill explicitly collects team updates via DM or channel, then redistributes and archives them, but provides no privacy notice, consent guidance, retention limits, or warning against sharing sensitive content. This creates a real privacy and data-governance risk because users may disclose personal, confidential, or security-sensitive information in what they assume is a limited-context conversation, only for it to be broadcast and stored.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
79% confidence
Finding

The example configuration hard-codes the timezone to "Asia/Shanghai", which can imply a fixed locale setting without user opt-in or explanation. For a general team standup skill, locale-sensitive defaults should either be presented as examples with explicit customization guidance or justified as region-specific.

Content

No source excerpt is available for this finding.