telegram-usage Security Audit Report
telegram-usage is an AI agent skill, created by c-drew and published at openclaw/skills. ClawSecure audited telegram-usage across 6 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 0/100 (High Risk). The 10 findings concentrate in Data Exfiltration, Policy Violation and Command Injection, including Pattern detected: require('child_process') and Pattern detected: execSync(. 8 were rated high or critical severity.
Is telegram-usage safe?
ClawSecure audited telegram-usage and assigned a security score of 0/100 (High Risk), identifying 10 findings across Data Exfiltration and Policy Violation. Review the findings below before installing.
What did ClawSecure find in telegram-usage?
ClawSecure identified 10 findings in telegram-usage, concentrated in Data Exfiltration, Policy Violation and Command Injection. 8 were rated high or critical severity. The most severe include Pattern detected: require('child_process') and Pattern detected: execSync(.
How was telegram-usage audited?
ClawSecure ran telegram-usage through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 6 files from openclaw/skills.
What does a score of 0 mean?
ClawSecure assigned telegram-usage a security score of 0/100, placing it in the High Risk range. This is driven by 10 findings led by Data Exfiltration that should be addressed before use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).
Audit Findings for telegram-usage
ClawSecure detected 10 security findings in telegram-usage, spanning Data Exfiltration, Policy Violation, Command Injection and Permissions Manifest.
- critical · Pattern detected: require('child_process'). Command Injection finding detected in
handler.js:10. - critical · Pattern detected: execSync(. Command Injection finding detected in
handler.js:48. - high · Only 61% of skill content could be analyzed. 2 of 6 files are opaque to.... Policy Violation finding.
- high · Pattern detected: fs.writeFileSync(. Data Exfiltration finding detected in
handler.js:118. - high · Pattern detected: fs.readFileSync(. Data Exfiltration finding detected in
handler.js:126. - high · Pattern detected: fs.writeFileSync(. Data Exfiltration finding detected in
handler.js:151. - high · Pattern detected: fs.readFileSync(. Data Exfiltration finding detected in
session-reader.js:80. - high · Pattern detected: fs.readFileSync(. Data Exfiltration finding detected in
session-reader.js:115. - medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
- info · Skill manifest does not include a 'license' field. Specifying a license.... Policy Violation finding detected in
SKILL.md.
Each finding is expandable in the interactive list below.
3-Layer Audit Protocol
Security Recommendations for telegram-usage
Audit external network connections
Resolve policy violations
Harden command execution
Related Security Research
ClawHavoc Explained: The Malware Family Targeting AI Agents→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→Related AI Agent Security Audits
Scanned on April 30, 2026. telegram-usage is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.