other
- Location
auto-attach.sh:7- Finding
Unrestricted Automatic Exfiltration of Workspace Files to Telegram
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is clearly intended to send workspace files to Telegram, but its implementation can automatically transmit any changed workspace file, not just documented file types, without per-file review.
Review this skill carefully before installing. It will run a watcher and can automatically send changed workspace files to Telegram; as written, it does not limit itself to documentation file types or ask before each send. Use only in a tightly controlled workspace with no secrets, credentials, private source, or sensitive files, and prefer a version with an explicit allowlist and confirmation step.
auto-attach.sh:7Unrestricted Automatic Exfiltration of Workspace Files to Telegram
auto-attach.sh:8Predictable Shared Temporary Paths Permit Symlink Attacks, Collisions, and Local Data Exposure
The skill explicitly states it monitors workspace files and automatically sends new or updated documentation files to Telegram, but it does not present this as a prominent user warning or require explicit opt-in at the point of use. This creates a real risk of unintended exfiltration of sensitive local content, especially because file-change triggers are automatic and the destination is an external messaging channel.
Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
log "Auto-attach script started. Watching $WATCH_DIR"
# Clean up temp files on exit
trap 'log "Script exiting - cleaning temp files"; rm -f "$TMP_DIR"/*; log "Watcher stopped"' EXIT INT TERM
# Watch for file changes
inotifywait -m -e create,modify -r --format '%w%f %e' "$WATCH_DIR" | while read -r file_path event; do
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
log "Auto-attach script started. Watching $WATCH_DIR"
# Clean up temp files on exit
trap 'log "Script exiting - cleaning temp files"; rm -f "$TMP_DIR"/*; log "Watcher stopped"' EXIT INT TERM
# Watch for file changes
inotifywait -m -e create,modify -r --format '%w%f %e' "$WATCH_DIR" | while read -r file_path event; do
Changed files are transmitted to Telegram automatically with no user-facing warning, approval step, or visibility into what content is being sent. This makes accidental disclosure of sensitive files very likely, especially because the watcher runs continuously over the workspace.
The script monitors the entire workspace and automatically sends changed files to Telegram, which is an external messaging service, without any apparent scoping, allowlist, or stated business justification. In the absence of a manifest or explicit user consent flow, this is effectively continuous data exfiltration of potentially sensitive workspace contents.
The manifest declares broad event triggers, "file-creation" and "file-modification," without any visible scoping, filtering, or path restrictions. In a skill described as automatically attaching files for Telegram, this can cause the skill to process unintended files, including sensitive or transient data, increasing the chance of unauthorized exfiltration or privacy-impacting behavior.
No suspicious patterns detected.