CtrlK
BlogDocsLog inGet started
Tessl Logo

hardcoded-creds

Systematic hunt for hardcoded credentials, API keys, certificates, and default passwords in extracted IoT firmware. Covers /etc/shadow and passwd parsing, busybox httpd configs, telnet/dropbear stanzas, MQTT/cloud API key extraction, and cross-referencing against known default-credential databases.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/iot/hardcoded-creds/SKILL.md
SKILL.md
Quality
Evals
Security

Security

2 findings: 1 critical severity, 1 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.

Critical

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 playbook explicitly instructs how to discover, extract, and crack embedded credentials and private keys from firmware (including host keys, authorized_keys, cloud tokens, JWTs), and discusses using those artifacts for SSH access and MitM—enabling credential theft, unauthorized access, and large-scale compromise.

Report incorrect finding
High

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 runs commands that extract and print plaintext/hashed passwords, API tokens, JWTs, and private keys and saves cracked plaintexts to evidence files, which requires the agent/LLM to handle and potentially output secret values verbatim.

Low

Low-risk findings.

1 low severity finding. Worth noting, but not necessarily harmful.

Low

W011: Third-party content exposure detected (indirect prompt injection risk).

What this means

The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.

Why it was flagged

This required workflow operates on extracted rootfs files from a provided/targeted firmware image (`/tmp/squashfs_root`), and it ingests that outsider-authored content into the LLM context indirectly via evidence strings/captured findings (e.g., printing/searching/cracked outputs such as `/tmp/all_strings.txt`, `/tmp/unshadowed.txt`, and evidence files), which would be treated as text derived from the outsider firmware rather than operating-user-authored data.

Repository
PurpleAILAB/Decepticon
Audited
Security analysis
Snyk

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.