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. 59 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/SKILL.md b/SKILL.md --- a/SKILL.md +++ b/SKILL.md @@ -95,1 +95,0 @@ --t "<prompt>" [-i ./local.png | --image-url <url>] [-f ./first.png -l ./last.png] \ @@ -98,1 +97,0 @@ -<skill_dir>/scripts/seedance --api-type openai-video --env-file <skill_dir>/.env -t "<prompt>" ... @@ -99,1 +97,0 @@ -<skill_dir>/scripts/seedance --api-type openai --env-file <skill_dir>/.env -t "<prompt>" ... diff --git a/scripts/seedance.py b/scripts/seedance.py --- a/scripts/seedance.py +++ b/scripts/seedance.py @@ -225,1 +225,0 @@ -"ARK_API_KEY is required. Set it in the environment or pass api_key=..."
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.2.1. 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: seedance: Fake instruction boundary tag (KillerSkills verdict caution 59)
## 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 59/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/clawhub/seedance/1.2.1 ## Findings with a location - `SKILL.md:95` · Fake instruction boundary tag — SKILL.md:95 · Fake instruction boundary tag - `SKILL.md:98` · Fake instruction boundary tag — SKILL.md:98 · Fake instruction boundary tag - `SKILL.md:99` · Fake instruction boundary tag — SKILL.md:99 · Fake instruction boundary tag - `scripts/seedance.py:225` · Credential pass-through configuration — scripts/seedance.py:225 · Credential pass-through configuration — agent relays sensitive credentials ## Proposed change The attached patch removes the 4 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._
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.