docker/skills docker-sandboxes-kits
Checked the catalogued skill at docker-sandboxes-kits.
D; retained sample includes a high finding · SD-007 · what this rule accepts as a false positive →
F; retained sample includes a high finding · SD-003 · what this rule accepts as a false positive →
B set by findings not listed in the stored summary
23 suppressed by AI triage
Documentation mentions a dynamic DNS hostname for a legitimate network request, not actual exfiltration.
The /tmp path is used for temporary Docker build output, a legitimate operation.
The /tmp path is again used for temporary Docker build output, a legitimate operation.
The file contains only empty lines; no Base64 encoding or decoding commands are present.
Only blank content appears; no obfuscated Base64 data can be detected.
The scanned content shows no Base64 strings or commands; likely a false positive.
No evidence of Base64 obfuscation in the file; empty lines only.
No Base64 payload present; the file is documentation with only empty lines, so the detection is a false positive.
Only whitespace is present; no malicious Base64 usage detected.
The file has no Base64 encoded data; scanner likely flagged a false positive.
No Base64 content or obfuscation found in the documentation.
Only empty lines present; no evidence of Base64 usage.
No Base64 strings or decoding commands are present.
The context shows no Base64 obfuscation; likely a scanner error.
File content contains only blanks; no malicious Base64 detected.
The snippet is part of documentation with no executable code, simply referencing base64 usage.
No Base64 obfuscation or commands are present in the file.
The content is documentation; no actual path traversal is present.
The file contains no actual ../ or absolute path references, just empty lines, so it is not a real path traversal threat.
The file is documentation that only illustrates using a temporary directory; no executable code is present.
The snippet is explanatory, showing how to create a temp directory for sandboxing, not an active path traversal.
This is a documented fallback path for cleanup; no executable code exploits are evident.
The file is documentation and contains only a descriptive note, not an active DNS exfiltration configuration.