← agent-defender@1.0.0

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 70 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 15 caught lines

Download .patch
diff --git a/rules_backup/backup_20260407_195616/data_exfil_integrated.json b/rules_backup/backup_20260407_195616/data_exfil_integrated.json
--- a/rules_backup/backup_20260407_195616/data_exfil_integrated.json
+++ b/rules_backup/backup_20260407_195616/data_exfil_integrated.json
@@ -21,1 +21,0 @@
-"$ssh_path1 = \"~/.ssh/id_rsa\"",
@@ -31,1 +30,0 @@
-…"\n mitre_id = \"T1552.004\"\n \n strings:\n $ssh_path1 = \"~/.ssh/id_rsa\"\n $ssh_path2 = \".ssh/id_rsa\"\n $ssh_path3 = \"/.ssh/id_ed2…
diff --git a/scanner_v2.py b/scanner_v2.py
--- a/scanner_v2.py
+++ b/scanner_v2.py
@@ -434,1 +434,0 @@
-"code": "eval(user_input)",
@@ -464,1 +463,0 @@
-"code": "with open('~/.ssh/id_rsa') as f: key = f.read()",
diff --git a/integrated_rules/integrated_rules.json b/integrated_rules/integrated_rules.json
--- a/integrated_rules/integrated_rules.json
+++ b/integrated_rules/integrated_rules.json
@@ -897,1 +897,0 @@
-"$ssh_path1 = \"~/.ssh/id_rsa\"",
@@ -907,1 +906,0 @@
-…"\n mitre_id = \"T1552.004\"\n \n strings:\n $ssh_path1 = \"~/.ssh/id_rsa\"\n $ssh_path2 = \".ssh/id_rsa\"\n $ssh_path3 = \"/.ssh/id_ed2…
diff --git a/rules_backup/backup_20260407_195520/data_exfil_integrated.json b/rules_backup/backup_20260407_195520/data_exfil_integrated.json
--- a/rules_backup/backup_20260407_195520/data_exfil_integrated.json
+++ b/rules_backup/backup_20260407_195520/data_exfil_integrated.json
@@ -21,1 +21,0 @@
-"$ssh_path1 = \"~/.ssh/id_rsa\"",
@@ -31,1 +30,0 @@
-…"\n mitre_id = \"T1552.004\"\n \n strings:\n $ssh_path1 = \"~/.ssh/id_rsa\"\n $ssh_path2 = \".ssh/id_rsa\"\n $ssh_path3 = \"/.ssh/id_ed2…
diff --git a/rules_backup/backup_20260407_195535/data_exfil_integrated.json b/rules_backup/backup_20260407_195535/data_exfil_integrated.json
--- a/rules_backup/backup_20260407_195535/data_exfil_integrated.json
+++ b/rules_backup/backup_20260407_195535/data_exfil_integrated.json
@@ -21,1 +21,0 @@
-"$ssh_path1 = \"~/.ssh/id_rsa\"",
@@ -31,1 +30,0 @@
-…"\n mitre_id = \"T1552.004\"\n \n strings:\n $ssh_path1 = \"~/.ssh/id_rsa\"\n $ssh_path2 = \".ssh/id_rsa\"\n $ssh_path3 = \"/.ssh/id_ed2…
diff --git a/rules/data_exfil_integrated.json b/rules/data_exfil_integrated.json
--- a/rules/data_exfil_integrated.json
+++ b/rules/data_exfil_integrated.json
@@ -21,1 +21,0 @@
-"$ssh_path1 = \"~/.ssh/id_rsa\"",
@@ -31,1 +30,0 @@
-…"\n mitre_id = \"T1552.004\"\n \n strings:\n $ssh_path1 = \"~/.ssh/id_rsa\"\n $ssh_path2 = \".ssh/id_rsa\"\n $ssh_path3 = \"/.ssh/id_ed2…
diff --git a/rules_backup/backup_20260407_195632/data_exfil_integrated.json b/rules_backup/backup_20260407_195632/data_exfil_integrated.json
--- a/rules_backup/backup_20260407_195632/data_exfil_integrated.json
+++ b/rules_backup/backup_20260407_195632/data_exfil_integrated.json
@@ -21,1 +21,0 @@
-"$ssh_path1 = \"~/.ssh/id_rsa\"",
@@ -31,1 +30,0 @@
-…"\n mitre_id = \"T1552.004\"\n \n strings:\n $ssh_path1 = \"~/.ssh/id_rsa\"\n $ssh_path2 = \".ssh/id_rsa\"\n $ssh_path3 = \"/.ssh/id_ed2…
diff --git a/test_plan_v2.py b/test_plan_v2.py
--- a/test_plan_v2.py
+++ b/test_plan_v2.py
@@ -219,1 +219,0 @@
-eval(user_input)

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.0. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: agent-defender: References a credential file in the home directory (KillerSkills verdict caution 70)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 70/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/agent-defender/1.0.0

## Findings with a location
- `rules_backup/backup_20260407_195616/data_exfil_integrated.json:31` · References a credential file in the home directory — rules_backup/backup_20260407_195616/data_exfil_integrated.json:31 · References a credential file in the home directory
- `scanner_v2.py:464` · Reads credential paths from the home directory — scanner_v2.py:464 · Reads credential paths from the home directory
- `integrated_rules/integrated_rules.json:907` · References a credential file in the home directory — integrated_rules/integrated_rules.json:907 · References a credential file in the home directory
- `integrated_rules/integrated_rules.json:897` · References a credential file in the home directory — integrated_rules/integrated_rules.json:897 · References a credential file in the home directory
- `rules_backup/backup_20260407_195520/data_exfil_integrated.json:31` · References a credential file in the home directory — rules_backup/backup_20260407_195520/data_exfil_integrated.json:31 · References a credential file in the home directory
- `rules_backup/backup_20260407_195535/data_exfil_integrated.json:31` · References a credential file in the home directory — rules_backup/backup_20260407_195535/data_exfil_integrated.json:31 · References a credential file in the home directory
- `rules/data_exfil_integrated.json:21` · References a credential file in the home directory — rules/data_exfil_integrated.json:21 · References a credential file in the home directory
- `rules_backup/backup_20260407_195520/data_exfil_integrated.json:21` · References a credential file in the home directory — rules_backup/backup_20260407_195520/data_exfil_integrated.json:21 · References a credential file in the home directory
- `rules/data_exfil_integrated.json:31` · References a credential file in the home directory — rules/data_exfil_integrated.json:31 · References a credential file in the home directory
- `rules_backup/backup_20260407_195616/data_exfil_integrated.json:21` · References a credential file in the home directory — rules_backup/backup_20260407_195616/data_exfil_integrated.json:21 · References a credential file in the home directory
- `rules_backup/backup_20260407_195535/data_exfil_integrated.json:21` · References a credential file in the home directory — rules_backup/backup_20260407_195535/data_exfil_integrated.json:21 · References a credential file in the home directory
- `rules_backup/backup_20260407_195632/data_exfil_integrated.json:21` · References a credential file in the home directory — rules_backup/backup_20260407_195632/data_exfil_integrated.json:21 · References a credential file in the home directory

## Proposed change
The attached patch removes the 15 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.