Versioned security assessment

Report ID: SA-80FD530D

6/28/2026, 6:35:40 AM

webapp-sqlmap security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
webapp-sqlmap
Version
v6
Maintainer
AgentSecOps
Coverage
5 Files scanned · 1,984 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

The static findings are mixed: generic reference templates create many false positives, but the main skill contains confirmed dual-use offensive sqlmap guidance. The skill is not deceptive and includes authorization warnings, but it provides explicit workflows for data extraction, file access, OS shells, WAF evasion, and Tor use, so it should not be published without strict marketplace controls.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

5 Files scanned · 1,984 Lines analyzed

5 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Observed in 3 evidence locations

Network access

May connect to external services.

Observed in 4 evidence locations

Filesystem access

May read or write local files.

Observed in 4 evidence locations

Env variables

May read values from the process environment.

Observed in 3 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 5 evidence locations

Capability review items (5)
High
Dual-use SQL injection exploitation workflow
The main skill goes beyond detection and instructs users on database enumeration, table dumping, credential extraction, server file reads, file writes, and OS shell access. These are legitimate in authorized tests but can directly enable unauthorized compromise.
The cited sections explicitly describe data extraction, file access, and shell options in an sqlmap workflow. Authorization warnings reduce malicious-intent confidence but not operational risk.
High
WAF bypass and anonymity guidance
The skill teaches tamper scripts, random user agents, proxy use, Tor checks, method changes, and randomized delays. These techniques can support authorized testing, but they also lower barriers for evasion during unauthorized attacks.
The cited sections are semantically about bypassing blocking controls and changing request behavior. Legitimate security testing is possible, but evasion content is clearly present.
High
Unsafe pipe-to-shell installer pattern in CI template
The CI template includes a curl-to-shell installation pattern. If copied into a workflow, this executes remote code from the network during CI and creates supply-chain risk.
The pattern is a real remote-code execution risk in CI templates. It appears educational rather than malicious, but the dangerous usage is concrete.
Medium
Operational execution examples require strong scope controls
Many static external-command and network findings come from sqlmap command examples against example domains. The commands are not executed by the skill itself, but they are actionable instructions for invasive network testing.
The examples are documented commands rather than hidden code execution. Risk remains elevated because they are intended to be run by the user against web targets.
Medium
Credential and environment examples are mostly benign templates
The scanner flagged environment variables, token names, and secret examples in rule and CI templates. These are mostly demonstrative security-scanning examples, but they can normalize copying placeholder secrets or broad token access if used carelessly.
The semantic context is defensive examples and GitHub Actions configuration, so most secret hits are false positives. The confidence is medium because templates can still be copied into real workflows.

Risk findings

Confirmed security concerns are separated from items that still need review.

No confirmed security findings were recorded for this completed audit.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (2)
Low
Static script and crypto hits in references are false positives
The document.write, innerHTML, MD5, SHA1, and API key patterns in the reference files are vulnerable-code examples used to teach detection and remediation. No evidence found that they are executable skill logic or hidden malicious behavior.
The surrounding text labels these snippets as examples, vulnerable patterns, and remediation material. This strongly supports a false-positive evaluation for those static hits.
Low
Prompt injection search found no evidence
No evidence found in the analyzed files for override instructions, fake system messages, pre-approval claims, or instructions to skip security review.
A targeted case-insensitive search across the listed files found no matching prompt-injection indicators. The confidence is high but limited to the inspected repository contents.

Verify and export

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable