← Back to Scanner

telegram-ops Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

telegram-ops is an AI agent skill, created by brennerspear and published at openclaw/skills. ClawSecure audited telegram-ops across 5 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 15/100 (High Risk). The 6 findings concentrate in Command Injection, Policy Violation and Permissions Manifest, including Detects command injection patterns in agent skills: shell operators,... and Detects command injection patterns in agent skills: shell operators,.... 4 were rated high or critical severity.

Is telegram-ops safe?

ClawSecure audited telegram-ops and assigned a security score of 15/100 (High Risk), identifying 6 findings across Command Injection and Policy Violation. Review the findings below before installing.

What did ClawSecure find in telegram-ops?

ClawSecure identified 6 findings in telegram-ops, concentrated in Command Injection, Policy Violation and Permissions Manifest. 4 were rated high or critical severity. The most severe include Detects command injection patterns in agent skills: shell operators,... and Detects command injection patterns in agent skills: shell operators,....

How was telegram-ops audited?

ClawSecure ran telegram-ops through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 5 files from openclaw/skills.

What does a score of 15 mean?

ClawSecure assigned telegram-ops a security score of 15/100, placing it in the High Risk range. This is driven by 6 findings led by Command Injection 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-ops

ClawSecure detected 6 security findings in telegram-ops, spanning Command Injection, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for telegram-ops

Harden command execution
telegram-ops constructs or runs system commands. Validate that commands are built only from trusted inputs, never pass user-controlled strings directly to a shell, and restrict execution to an allow-list of expected commands.
Resolve policy violations
telegram-ops trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.

Related Security Research

Why Generic Scanners Fail at AI Agent SecurityUnderstanding Our 3-Layer Audit Protocol

Related AI Agent Security Audits

lossless-clawScore 25/100qiaomu-mondo-poster-designScore 0/100proactive-agentScore 0/100zoho-email-integrationScore 0/100zoho-email-integrationScore 0/100

Scanned on February 7, 2026. telegram-ops is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan