← workspace-backup-github@1.3.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. 55 · Caution

Evidence

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

Diff · removes 5 caught lines

Download .patch
diff --git a/scripts/backup.sh b/scripts/backup.sh
--- a/scripts/backup.sh
+++ b/scripts/backup.sh
@@ -26,1 +26,0 @@
-EXPECTED_REMOTE="https://x-access-token:${TOKEN}@github.com/${GITHUB_USER}/${REPO_NAME}.git"
@@ -34,1 +33,0 @@
-git add AGENTS.md SOUL.md USER.md IDENTITY.md TOOLS.md HEARTBEAT.md README.md SYNC.md .gitignore skills/ memory/ 2>/dev/null
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -80,1 +80,0 @@
-> 6. Copy and paste the Token here
@@ -168,1 +167,0 @@
-git remote set-url origin https://x-access-token:[email protected]/user/repo.git
@@ -175,1 +173,0 @@
-git add skills/ memory/ AGENTS.md SOUL.md USER.md IDENTITY.md TOOLS.md HEARTBEAT.md README.md SYNC.md .gitignore

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.3.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: workspace-backup-github: URL with embedded credentials (KillerSkills verdict caution 55)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 55/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/workspace-backup-github/1.3.0

## Findings with a location
- `scripts/backup.sh:26` · URL with embedded credentials — scripts/backup.sh:26 · URL with embedded credentials — may be phishing or credential leaking
- `SKILL.md:168` · URL with embedded credentials — SKILL.md:168 · URL with embedded credentials — may be phishing or credential leaking
- `SKILL.md:175` · Instructs the agent to modify its persistent memory or instruction files — SKILL.md:175 · Instructs the agent to modify its persistent memory or instruction files
- `SKILL.md:80` · Prompting user to enter sensitive credentials — SKILL.md:80 · Prompting user to enter sensitive credentials — social engineering
- `scripts/backup.sh:34` · Instructs the agent to modify its persistent memory or instruction files — scripts/backup.sh:34 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file

## Proposed change
The attached patch removes the 5 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._
# or from a terminal, under your own account:
gh repo fork settings/tokens --clone && cd tokens
curl -s https://killerskills.ai/skills/clawhub/workspace-backup-github/1.3.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.3.0 && git commit -am "workspace-backup-github: URL with embedded credentials"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/workspace-backup-github/1.3.0/patch.md)

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.