@guava-parity/guard-scanner 13.0.0 → 16.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +170 -215
- package/README_ja.md +252 -0
- package/SECURITY.md +12 -4
- package/SKILL.md +148 -57
- package/dist/cli.cjs +5997 -0
- package/dist/cli.d.mts +1 -0
- package/dist/cli.d.ts +1 -0
- package/dist/cli.mjs +6003 -0
- package/dist/index.cjs +4825 -0
- package/dist/index.d.mts +17 -0
- package/dist/index.d.ts +17 -0
- package/dist/index.mjs +4798 -0
- package/dist/mcp-server.cjs +4756 -0
- package/dist/mcp-server.d.mts +1 -0
- package/dist/mcp-server.d.ts +1 -0
- package/dist/mcp-server.mjs +4767 -0
- package/dist/openclaw-plugin.cjs +4863 -0
- package/dist/openclaw-plugin.d.mts +11 -0
- package/dist/openclaw-plugin.d.ts +11 -0
- package/dist/openclaw-plugin.mjs +4854 -0
- package/dist/types.cjs +18 -0
- package/dist/types.d.mts +215 -0
- package/dist/types.d.ts +215 -0
- package/dist/types.mjs +1 -0
- package/docs/EVIDENCE_DRIVEN.md +182 -0
- package/docs/banner.png +0 -0
- package/docs/data/benchmark-ledger.json +1428 -0
- package/docs/data/corpus-metrics.json +11 -0
- package/docs/data/fp-ledger.json +18 -0
- package/docs/data/latest.json +25837 -2481
- package/docs/data/quality-contract.json +36 -0
- package/docs/generated/npm-audit-20260312.json +96 -0
- package/docs/generated/openclaw-upstream-status.json +25 -0
- package/docs/glossary.md +46 -0
- package/docs/index.html +1085 -496
- package/docs/logo.png +0 -0
- package/docs/openclaw-compatibility-audit.md +45 -0
- package/docs/openclaw-continuous-compatibility-plan.md +37 -0
- package/docs/rules/a2a-contagion.md +68 -0
- package/docs/rules/advanced-exfil.md +52 -0
- package/docs/rules/agent-protocol.md +108 -0
- package/docs/rules/api-abuse.md +68 -0
- package/docs/rules/autonomous-risk.md +92 -0
- package/docs/rules/config-impact.md +132 -0
- package/docs/rules/credential-handling.md +100 -0
- package/docs/rules/cve-patterns.md +332 -0
- package/docs/rules/data-exposure.md +84 -0
- package/docs/rules/exfiltration.md +36 -0
- package/docs/rules/financial-access.md +84 -0
- package/docs/rules/identity-hijack.md +140 -0
- package/docs/rules/inference-manipulation.md +60 -0
- package/docs/rules/leaky-skills.md +52 -0
- package/docs/rules/malicious-code.md +108 -0
- package/docs/rules/mcp-security.md +148 -0
- package/docs/rules/memory-poisoning.md +84 -0
- package/docs/rules/model-poisoning.md +44 -0
- package/docs/rules/obfuscation.md +60 -0
- package/docs/rules/persistence.md +108 -0
- package/docs/rules/pii-exposure.md +116 -0
- package/docs/rules/prompt-injection.md +148 -0
- package/docs/rules/prompt-worm.md +44 -0
- package/docs/rules/safeguard-bypass.md +44 -0
- package/docs/rules/sandbox-escape.md +100 -0
- package/docs/rules/secret-detection.md +44 -0
- package/docs/rules/supply-chain-v2.md +92 -0
- package/docs/rules/suspicious-download.md +60 -0
- package/docs/rules/trust-boundary.md +76 -0
- package/docs/rules/trust-exploitation.md +92 -0
- package/docs/rules/unverifiable-deps.md +84 -0
- package/docs/rules/vdb-injection.md +84 -0
- package/docs/security-vulnerability-report-20260312.md +53 -0
- package/docs/spec/PRD_V2_ARCHITECTURE.md +55 -0
- package/docs/spec/capabilities.json +174 -0
- package/docs/spec/finding.schema.json +104 -0
- package/docs/spec/integration-manifest.md +39 -0
- package/docs/spec/plugin-trust.json +11 -0
- package/docs/spec/sbom.json +33 -0
- package/docs/threat-model.md +65 -0
- package/docs/v13-architecture-manifest.md +55 -0
- package/hooks/context.ts +306 -0
- package/hooks/guard-scanner/plugin.ts +24 -1
- package/openclaw-plugin.mts +107 -0
- package/openclaw.plugin.json +30 -53
- package/package.json +66 -13
- package/src/asset-auditor.js +0 -508
- package/src/ci-reporter.js +0 -135
- package/src/cli.js +0 -294
- package/src/html-template.js +0 -239
- package/src/ioc-db.js +0 -54
- package/src/mcp-server.js +0 -702
- package/src/patterns.js +0 -611
- package/src/quarantine.js +0 -41
- package/src/runtime-guard.js +0 -346
- package/src/scanner.js +0 -1157
- package/src/vt-client.js +0 -202
- package/src/watcher.js +0 -170
|
@@ -0,0 +1,60 @@
|
|
|
1
|
+
# Threat Category: obfuscation
|
|
2
|
+
|
|
3
|
+
This document provides explainability for all rules in the `obfuscation` category.
|
|
4
|
+
|
|
5
|
+
## Rule: `OBF_HEX`
|
|
6
|
+
- **Severity**: HIGH
|
|
7
|
+
- **Description**: Hex-encoded string (5+ bytes)
|
|
8
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
9
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
10
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
11
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
12
|
+
|
|
13
|
+
## Rule: `OBF_BASE64_EXEC`
|
|
14
|
+
- **Severity**: CRITICAL
|
|
15
|
+
- **Description**: Base64 decode → execute chain
|
|
16
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
17
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
18
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
19
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
20
|
+
|
|
21
|
+
## Rule: `OBF_BASE64`
|
|
22
|
+
- **Severity**: MEDIUM
|
|
23
|
+
- **Description**: Base64 decoding
|
|
24
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
25
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
26
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
27
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
28
|
+
|
|
29
|
+
## Rule: `OBF_CHARCODE`
|
|
30
|
+
- **Severity**: HIGH
|
|
31
|
+
- **Description**: Character code construction (4+ chars)
|
|
32
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
33
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
34
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
35
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
36
|
+
|
|
37
|
+
## Rule: `OBF_CONCAT`
|
|
38
|
+
- **Severity**: MEDIUM
|
|
39
|
+
- **Description**: Array join obfuscation
|
|
40
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
41
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
42
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
43
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
44
|
+
|
|
45
|
+
## Rule: `OBF_BASE64_BASH`
|
|
46
|
+
- **Severity**: CRITICAL
|
|
47
|
+
- **Description**: Base64 decode piped to shell
|
|
48
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
49
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
50
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
51
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
52
|
+
|
|
53
|
+
## Rule: `LLM_SCANNER_EVASION`
|
|
54
|
+
- **Severity**: HIGH
|
|
55
|
+
- **Description**: LLM scanner evasion: adversarial comment claiming code is safe
|
|
56
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
57
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
58
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
59
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
60
|
+
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# Threat Category: persistence
|
|
2
|
+
|
|
3
|
+
This document provides explainability for all rules in the `persistence` category.
|
|
4
|
+
|
|
5
|
+
## Rule: `PERSIST_CRON`
|
|
6
|
+
- **Severity**: HIGH
|
|
7
|
+
- **Description**: Persistence: scheduled task creation
|
|
8
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
9
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
10
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
11
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
12
|
+
|
|
13
|
+
## Rule: `PERSIST_STARTUP`
|
|
14
|
+
- **Severity**: HIGH
|
|
15
|
+
- **Description**: Persistence: startup execution
|
|
16
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
17
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
18
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
19
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
20
|
+
|
|
21
|
+
## Rule: `PERSIST_LAUNCHD`
|
|
22
|
+
- **Severity**: HIGH
|
|
23
|
+
- **Description**: OS-level persistence mechanism
|
|
24
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
25
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
26
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
27
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
28
|
+
|
|
29
|
+
## Rule: `PERSIST_CRONTAB_INJECT`
|
|
30
|
+
- **Severity**: HIGH
|
|
31
|
+
- **Description**: Persistence: crontab manipulation for scheduled execution
|
|
32
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
33
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
34
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
35
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
36
|
+
|
|
37
|
+
## Rule: `PERSIST_LAUNCHD_PLIST`
|
|
38
|
+
- **Severity**: HIGH
|
|
39
|
+
- **Description**: Persistence: macOS LaunchAgent/Daemon installation
|
|
40
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
41
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
42
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
43
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
44
|
+
|
|
45
|
+
## Rule: `PERSIST_REGISTRY_RUN`
|
|
46
|
+
- **Severity**: HIGH
|
|
47
|
+
- **Description**: Persistence: Windows registry Run key modification
|
|
48
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
49
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
50
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
51
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
52
|
+
|
|
53
|
+
## Rule: `PERSIST_BASHRC_INJECT`
|
|
54
|
+
- **Severity**: HIGH
|
|
55
|
+
- **Description**: Persistence: shell profile injection (~/.bashrc, ~/.zshrc)
|
|
56
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
57
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
58
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
59
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
60
|
+
|
|
61
|
+
## Rule: `PERSIST_SSH_AUTHORIZED`
|
|
62
|
+
- **Severity**: CRITICAL
|
|
63
|
+
- **Description**: Persistence: SSH authorized_keys modification for backdoor access
|
|
64
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
65
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
66
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
67
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
68
|
+
|
|
69
|
+
## Rule: `PERSIST_SYSTEMD_SERVICE`
|
|
70
|
+
- **Severity**: HIGH
|
|
71
|
+
- **Description**: Persistence: systemd service installation
|
|
72
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
73
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
74
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
75
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
76
|
+
|
|
77
|
+
## Rule: `EVASION_FILELESS`
|
|
78
|
+
- **Severity**: CRITICAL
|
|
79
|
+
- **Description**: Evasion: fileless execution via memory-backed file descriptors
|
|
80
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
81
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
82
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
83
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
84
|
+
|
|
85
|
+
## Rule: `EVASION_LOG_TAMPER`
|
|
86
|
+
- **Severity**: HIGH
|
|
87
|
+
- **Description**: Evasion: shell history clearing to hide activity
|
|
88
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
89
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
90
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
91
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
92
|
+
|
|
93
|
+
## Rule: `EVASION_TIMESTAMP_STOMP`
|
|
94
|
+
- **Severity**: HIGH
|
|
95
|
+
- **Description**: Evasion: file timestamp manipulation (timestomping)
|
|
96
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
97
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
98
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
99
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
100
|
+
|
|
101
|
+
## Rule: `EVASION_PACKED_PAYLOAD`
|
|
102
|
+
- **Severity**: HIGH
|
|
103
|
+
- **Description**: Evasion: packed/protected binary to evade analysis
|
|
104
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
105
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
106
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
107
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
108
|
+
|
|
@@ -0,0 +1,116 @@
|
|
|
1
|
+
# Threat Category: pii-exposure
|
|
2
|
+
|
|
3
|
+
This document provides explainability for all rules in the `pii-exposure` category.
|
|
4
|
+
|
|
5
|
+
## Rule: `PII_MY_NUMBER`
|
|
6
|
+
- **Severity**: CRITICAL
|
|
7
|
+
- **Description**: Potential My Number (個人番号)
|
|
8
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
9
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
10
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
11
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
12
|
+
|
|
13
|
+
## Rule: `PII_HARDCODED_CC`
|
|
14
|
+
- **Severity**: CRITICAL
|
|
15
|
+
- **Description**: Hardcoded credit card number
|
|
16
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
17
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
18
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
19
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
20
|
+
|
|
21
|
+
## Rule: `PII_HARDCODED_SSN`
|
|
22
|
+
- **Severity**: CRITICAL
|
|
23
|
+
- **Description**: Hardcoded SSN/tax ID
|
|
24
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
25
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
26
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
27
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
28
|
+
|
|
29
|
+
## Rule: `PII_HARDCODED_PHONE`
|
|
30
|
+
- **Severity**: HIGH
|
|
31
|
+
- **Description**: Hardcoded phone number
|
|
32
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
33
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
34
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
35
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
36
|
+
|
|
37
|
+
## Rule: `PII_HARDCODED_EMAIL`
|
|
38
|
+
- **Severity**: HIGH
|
|
39
|
+
- **Description**: Hardcoded email address
|
|
40
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
41
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
42
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
43
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
44
|
+
|
|
45
|
+
## Rule: `PII_LOG_SENSITIVE`
|
|
46
|
+
- **Severity**: HIGH
|
|
47
|
+
- **Description**: PII variable logged to console
|
|
48
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
49
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
50
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
51
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
52
|
+
|
|
53
|
+
## Rule: `PII_SEND_NETWORK`
|
|
54
|
+
- **Severity**: CRITICAL
|
|
55
|
+
- **Description**: PII variable sent over network
|
|
56
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
57
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
58
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
59
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
60
|
+
|
|
61
|
+
## Rule: `PII_STORE_PLAINTEXT`
|
|
62
|
+
- **Severity**: HIGH
|
|
63
|
+
- **Description**: PII stored in plaintext file
|
|
64
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
65
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
66
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
67
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
68
|
+
|
|
69
|
+
## Rule: `SHADOW_AI_OPENAI`
|
|
70
|
+
- **Severity**: HIGH
|
|
71
|
+
- **Description**: Shadow AI: OpenAI API call
|
|
72
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
73
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
74
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
75
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
76
|
+
|
|
77
|
+
## Rule: `SHADOW_AI_ANTHROPIC`
|
|
78
|
+
- **Severity**: HIGH
|
|
79
|
+
- **Description**: Shadow AI: Anthropic API call
|
|
80
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
81
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
82
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
83
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
84
|
+
|
|
85
|
+
## Rule: `SHADOW_AI_GENERIC`
|
|
86
|
+
- **Severity**: MEDIUM
|
|
87
|
+
- **Description**: Shadow AI: generic LLM API endpoint
|
|
88
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
89
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
90
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
91
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
92
|
+
|
|
93
|
+
## Rule: `PII_ASK_ADDRESS`
|
|
94
|
+
- **Severity**: HIGH
|
|
95
|
+
- **Description**: PII collection: home address
|
|
96
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
97
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
98
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
99
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
100
|
+
|
|
101
|
+
## Rule: `PII_ASK_DOB`
|
|
102
|
+
- **Severity**: HIGH
|
|
103
|
+
- **Description**: PII collection: date of birth
|
|
104
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
105
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
106
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
107
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
108
|
+
|
|
109
|
+
## Rule: `PII_ASK_GOV_ID`
|
|
110
|
+
- **Severity**: CRITICAL
|
|
111
|
+
- **Description**: PII collection: government ID
|
|
112
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
113
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
114
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
115
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
116
|
+
|
|
@@ -0,0 +1,148 @@
|
|
|
1
|
+
# Threat Category: prompt-injection
|
|
2
|
+
|
|
3
|
+
This document provides explainability for all rules in the `prompt-injection` category.
|
|
4
|
+
|
|
5
|
+
## Rule: `PI_IGNORE`
|
|
6
|
+
- **Severity**: CRITICAL
|
|
7
|
+
- **Description**: Prompt injection: ignore instructions
|
|
8
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
9
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
10
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
11
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
12
|
+
|
|
13
|
+
## Rule: `PI_ROLE`
|
|
14
|
+
- **Severity**: CRITICAL
|
|
15
|
+
- **Description**: Prompt injection: role override
|
|
16
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
17
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
18
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
19
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
20
|
+
|
|
21
|
+
## Rule: `PI_SYSTEM`
|
|
22
|
+
- **Severity**: CRITICAL
|
|
23
|
+
- **Description**: Prompt injection: system message impersonation
|
|
24
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
25
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
26
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
27
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
28
|
+
|
|
29
|
+
## Rule: `PI_ZWSP`
|
|
30
|
+
- **Severity**: CRITICAL
|
|
31
|
+
- **Description**: Zero-width Unicode (hidden text)
|
|
32
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
33
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
34
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
35
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
36
|
+
|
|
37
|
+
## Rule: `PI_BIDI`
|
|
38
|
+
- **Severity**: CRITICAL
|
|
39
|
+
- **Description**: Unicode BiDi control character (text direction attack)
|
|
40
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
41
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
42
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
43
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
44
|
+
|
|
45
|
+
## Rule: `PI_INVISIBLE`
|
|
46
|
+
- **Severity**: HIGH
|
|
47
|
+
- **Description**: Invisible/formatting Unicode character
|
|
48
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
49
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
50
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
51
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
52
|
+
|
|
53
|
+
## Rule: `PI_HOMOGLYPH`
|
|
54
|
+
- **Severity**: HIGH
|
|
55
|
+
- **Description**: Cyrillic/Latin homoglyph mixing
|
|
56
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
57
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
58
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
59
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
60
|
+
|
|
61
|
+
## Rule: `PI_HOMOGLYPH_GREEK`
|
|
62
|
+
- **Severity**: HIGH
|
|
63
|
+
- **Description**: Greek/Latin homoglyph mixing
|
|
64
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
65
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
66
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
67
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
68
|
+
|
|
69
|
+
## Rule: `PI_HOMOGLYPH_MATH`
|
|
70
|
+
- **Severity**: HIGH
|
|
71
|
+
- **Description**: Mathematical symbol homoglyphs (𝐀-𝟿)
|
|
72
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
73
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
74
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
75
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
76
|
+
|
|
77
|
+
## Rule: `PI_TAG_INJECTION`
|
|
78
|
+
- **Severity**: CRITICAL
|
|
79
|
+
- **Description**: XML/tag-based prompt injection
|
|
80
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
81
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
82
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
83
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
84
|
+
|
|
85
|
+
## Rule: `PI_BASE64_MD`
|
|
86
|
+
- **Severity**: CRITICAL
|
|
87
|
+
- **Description**: Base64 execution instruction in docs
|
|
88
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
89
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
90
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
91
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
92
|
+
|
|
93
|
+
## Rule: `MOLTBOOK_REVERSE_PI`
|
|
94
|
+
- **Severity**: CRITICAL
|
|
95
|
+
- **Description**: Moltbook Reverse Prompt Injection
|
|
96
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
97
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
98
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
99
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
100
|
+
|
|
101
|
+
## Rule: `AUTO_REFINE_A2A_IDPI`
|
|
102
|
+
- **Severity**: CRITICAL
|
|
103
|
+
- **Description**: A2A Contagion Indirect Prompt Injection (IDPI)
|
|
104
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
105
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
106
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
107
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
108
|
+
|
|
109
|
+
## Rule: `A2A_SEMANTIC_CONTAGION`
|
|
110
|
+
- **Severity**: CRITICAL
|
|
111
|
+
- **Description**: A2A Semantic Contagion passing downstream payload overrides
|
|
112
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
113
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
114
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
115
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
116
|
+
|
|
117
|
+
## Rule: `PI_TOKEN_SPLIT`
|
|
118
|
+
- **Severity**: HIGH
|
|
119
|
+
- **Description**: Token-splitting PI: fragmented "ignore" across delimiters
|
|
120
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
121
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
122
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
123
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
124
|
+
|
|
125
|
+
## Rule: `PI_FULLWIDTH_EVASION`
|
|
126
|
+
- **Severity**: HIGH
|
|
127
|
+
- **Description**: Fullwidth Latin evasion (NFKC bypass)
|
|
128
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
129
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
130
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
131
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
132
|
+
|
|
133
|
+
## Rule: `MOLTBOOK_INDIRECT_PI`
|
|
134
|
+
- **Severity**: CRITICAL
|
|
135
|
+
- **Description**: Moltbook Bot-to-Bot payload: hidden system instruction
|
|
136
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
137
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
138
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
139
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
140
|
+
|
|
141
|
+
## Rule: `SNYK_AGENT_GUARD_EVASION`
|
|
142
|
+
- **Severity**: CRITICAL
|
|
143
|
+
- **Description**: Snyk Agent Guard evasion using Cyrillic/Homoglyphs
|
|
144
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
145
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
146
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
147
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
148
|
+
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
# Threat Category: prompt-worm
|
|
2
|
+
|
|
3
|
+
This document provides explainability for all rules in the `prompt-worm` category.
|
|
4
|
+
|
|
5
|
+
## Rule: `WORM_SELF_REPLICATE`
|
|
6
|
+
- **Severity**: CRITICAL
|
|
7
|
+
- **Description**: Prompt worm: self-replication
|
|
8
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
9
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
10
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
11
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
12
|
+
|
|
13
|
+
## Rule: `WORM_SPREAD`
|
|
14
|
+
- **Severity**: CRITICAL
|
|
15
|
+
- **Description**: Prompt worm: agent-to-agent propagation
|
|
16
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
17
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
18
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
19
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
20
|
+
|
|
21
|
+
## Rule: `WORM_HIDDEN_INSTRUCT`
|
|
22
|
+
- **Severity**: CRITICAL
|
|
23
|
+
- **Description**: Prompt worm: hidden instruction embedding
|
|
24
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
25
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
26
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
27
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
28
|
+
|
|
29
|
+
## Rule: `WORM_CSS_HIDE`
|
|
30
|
+
- **Severity**: HIGH
|
|
31
|
+
- **Description**: CSS-hidden content (invisible to humans)
|
|
32
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
33
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
34
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
35
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
36
|
+
|
|
37
|
+
## Rule: `AUTO_REFINE_ZERO_WIDTH`
|
|
38
|
+
- **Severity**: CRITICAL
|
|
39
|
+
- **Description**: Zero-Width Prompt Injection Worm
|
|
40
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
41
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
42
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
43
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
44
|
+
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
# Threat Category: safeguard-bypass
|
|
2
|
+
|
|
3
|
+
This document provides explainability for all rules in the `safeguard-bypass` category.
|
|
4
|
+
|
|
5
|
+
## Rule: `REPROMPT_URL_PI`
|
|
6
|
+
- **Severity**: CRITICAL
|
|
7
|
+
- **Description**: URL parameter prompt injection
|
|
8
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
9
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
10
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
11
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
12
|
+
|
|
13
|
+
## Rule: `REPROMPT_DOUBLE`
|
|
14
|
+
- **Severity**: HIGH
|
|
15
|
+
- **Description**: Double-execution safeguard bypass
|
|
16
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
17
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
18
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
19
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
20
|
+
|
|
21
|
+
## Rule: `REPROMPT_RETRY`
|
|
22
|
+
- **Severity**: HIGH
|
|
23
|
+
- **Description**: Retry-on-block safeguard bypass
|
|
24
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
25
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
26
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
27
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
28
|
+
|
|
29
|
+
## Rule: `BYPASS_REPHRASE`
|
|
30
|
+
- **Severity**: CRITICAL
|
|
31
|
+
- **Description**: Instruction to rephrase to avoid filters
|
|
32
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
33
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
34
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
35
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
36
|
+
|
|
37
|
+
## Rule: `CLAUDE_SEC_SCAN_SUPPRESS`
|
|
38
|
+
- **Severity**: HIGH
|
|
39
|
+
- **Description**: Claude Code Security scan result suppression or bypass
|
|
40
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
41
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
42
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
43
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
44
|
+
|
|
@@ -0,0 +1,100 @@
|
|
|
1
|
+
# Threat Category: sandbox-escape
|
|
2
|
+
|
|
3
|
+
This document provides explainability for all rules in the `sandbox-escape` category.
|
|
4
|
+
|
|
5
|
+
## Rule: `SANDBOX_PROC_MOUNT`
|
|
6
|
+
- **Severity**: CRITICAL
|
|
7
|
+
- **Description**: Sandbox escape: /proc/self access for container breakout
|
|
8
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
9
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
10
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
11
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
12
|
+
|
|
13
|
+
## Rule: `SANDBOX_CHROOT_BREAK`
|
|
14
|
+
- **Severity**: CRITICAL
|
|
15
|
+
- **Description**: Sandbox escape: chroot/namespace manipulation
|
|
16
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
17
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
18
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
19
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
20
|
+
|
|
21
|
+
## Rule: `SANDBOX_DOCKER_SOCK`
|
|
22
|
+
- **Severity**: CRITICAL
|
|
23
|
+
- **Description**: Sandbox escape: Docker socket access or privileged exec
|
|
24
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
25
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
26
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
27
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
28
|
+
|
|
29
|
+
## Rule: `SANDBOX_SYMLINK_RACE`
|
|
30
|
+
- **Severity**: HIGH
|
|
31
|
+
- **Description**: Sandbox escape: symlink race condition to access restricted paths
|
|
32
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
33
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
34
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
35
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
36
|
+
|
|
37
|
+
## Rule: `SANDBOX_PTRACE`
|
|
38
|
+
- **Severity**: CRITICAL
|
|
39
|
+
- **Description**: Sandbox escape: ptrace-based process injection
|
|
40
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
41
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
42
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
43
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
44
|
+
|
|
45
|
+
## Rule: `SANDBOX_RLIMIT_BYPASS`
|
|
46
|
+
- **Severity**: HIGH
|
|
47
|
+
- **Description**: Sandbox escape: resource limit bypass
|
|
48
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
49
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
50
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
51
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
52
|
+
|
|
53
|
+
## Rule: `SANDBOX_MOUNT_NS`
|
|
54
|
+
- **Severity**: CRITICAL
|
|
55
|
+
- **Description**: Sandbox escape: filesystem mount in restricted namespace
|
|
56
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
57
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
58
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
59
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
60
|
+
|
|
61
|
+
## Rule: `SANDBOX_DBUS_ESCAPE`
|
|
62
|
+
- **Severity**: HIGH
|
|
63
|
+
- **Description**: Sandbox escape: D-Bus IPC exploitation (Flatpak/Snap)
|
|
64
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
65
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
66
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
67
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
68
|
+
|
|
69
|
+
## Rule: `SANDBOX_SECCOMP_BYPASS`
|
|
70
|
+
- **Severity**: CRITICAL
|
|
71
|
+
- **Description**: Sandbox escape: seccomp filter manipulation
|
|
72
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
73
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
74
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
75
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
76
|
+
|
|
77
|
+
## Rule: `SANDBOX_CGROUP_ESCAPE`
|
|
78
|
+
- **Severity**: CRITICAL
|
|
79
|
+
- **Description**: Sandbox escape: cgroup breakout via release_agent (CVE-2022-0492 variant)
|
|
80
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
81
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
82
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
83
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
84
|
+
|
|
85
|
+
## Rule: `SANDBOX_K8S_SA_TOKEN`
|
|
86
|
+
- **Severity**: CRITICAL
|
|
87
|
+
- **Description**: Sandbox escape: Kubernetes service account token theft
|
|
88
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
89
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
90
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
91
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
92
|
+
|
|
93
|
+
## Rule: `SANDBOX_WASM_ESCAPE`
|
|
94
|
+
- **Severity**: HIGH
|
|
95
|
+
- **Description**: WASM sandbox escape: WASI filesystem escape via mapped directories
|
|
96
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
97
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
98
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
99
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
100
|
+
|
|
@@ -0,0 +1,44 @@
|
|
|
1
|
+
# Threat Category: secret-detection
|
|
2
|
+
|
|
3
|
+
This document provides explainability for all rules in the `secret-detection` category.
|
|
4
|
+
|
|
5
|
+
## Rule: `SECRET_HARDCODED_KEY`
|
|
6
|
+
- **Severity**: HIGH
|
|
7
|
+
- **Description**: Hardcoded API key/secret
|
|
8
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
9
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
10
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
11
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
12
|
+
|
|
13
|
+
## Rule: `SECRET_PRIVATE_KEY`
|
|
14
|
+
- **Severity**: CRITICAL
|
|
15
|
+
- **Description**: Embedded private key
|
|
16
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
17
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
18
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
19
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
20
|
+
|
|
21
|
+
## Rule: `SECRET_GITHUB_TOKEN`
|
|
22
|
+
- **Severity**: CRITICAL
|
|
23
|
+
- **Description**: GitHub token
|
|
24
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
25
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
26
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
27
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
28
|
+
|
|
29
|
+
## Rule: `MOLTBOOK_SUPABASE_LEAK`
|
|
30
|
+
- **Severity**: CRITICAL
|
|
31
|
+
- **Description**: Supabase API Key (Moltbook 1.5M Leak pattern)
|
|
32
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
33
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
34
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
35
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
36
|
+
|
|
37
|
+
## Rule: `SECRET_ANTHROPIC_KEY_V2`
|
|
38
|
+
- **Severity**: CRITICAL
|
|
39
|
+
- **Description**: Anthropic API key v2 (sk-ant-api/msg/adm prefix)
|
|
40
|
+
- **Rationale**: Explains why this pattern is considered dangerous.
|
|
41
|
+
- **Exploit Precondition**: What an attacker needs to trigger this.
|
|
42
|
+
- **Likely False Positives**: Scenarios where this might trigger safely.
|
|
43
|
+
- **Remediation Hint**: How to fix or mitigate the finding.
|
|
44
|
+
|