ssti
Hunt server-side template injection across Jinja2/Twig/Freemarker/Velocity/Handlebars and validate progression from expression injection to code execution.
63
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Fix and improve this skill with Tessl
tessl review fix ./packages/decepticon/decepticon/skills/standard/analyst/ssti/SKILL.mdSecurity
3 findings: 1 critical severity, 1 high severity, 1 medium severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
E006: Malicious code pattern detected in skill scripts.
What this means
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
Why it was flagged
This is a clear exploitation playbook for Server-Side Template Injection (SSTI) that instructs probing, env/file leaks, and command execution—facilitating data exfiltration and remote code execution.
W007: Insecure credential handling detected in skill instructions.
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
The playbook explicitly instructs attempts to read and "env leak" environment variables and uses template probes like {{config}}/{{request}}, which requires retrieving and potentially embedding secret values verbatim in outputs.
W013: Attempt to modify system services in skill instructions.
What this means
The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.
Why it was flagged
The playbook explicitly instructs "Attempt file read / env leak" and "Attempt command execution via framework-specific gadget chain", which encourages actions that can access or execute commands on the host and thus may compromise the machine's state even though it doesn't directly request sudo or creating users.
- Repository
- PurpleAILAB/Decepticon
- Commit
0cf691e
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.