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. 64 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 2 caught lines
Download .patchdiff --git a/README.md b/README.md --- a/README.md +++ b/README.md @@ -37,1 +37,0 @@ -<summary><strong>Install from a local clone</strong> (for development or testing a branch)</summary> ```bash git clone https://github.com/CrowdStrike/fusion-ski diff --git a/skills/setup/SKILL.md b/skills/setup/SKILL.md --- a/skills/setup/SKILL.md +++ b/skills/setup/SKILL.md @@ -181,1 +181,0 @@ -not through the chat. Do **not** ask them to paste the secret into the chat.
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.4.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: crowdstrike-falcon-fusion: Collapsed <details> block carrying instructions (KillerSkills verdict caution 64)
## 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 64/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/plugins/crowdstrike-falcon-fusion/1.4.0 ## Findings with a location - `README.md:37` · Collapsed <details> block carrying instructions — README.md:37 · Collapsed <details> block carrying instructions - `skills/setup/SKILL.md:181` · Prompting user to enter sensitive credentials — skills/setup/SKILL.md:181 · Prompting user to enter sensitive credentials — social engineering ## Proposed change The attached patch removes the 2 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 CrowdStrike/fusion-skills --clone && cd fusion-skills curl -s https://killerskills.ai/skills/plugins/crowdstrike-falcon-fusion/1.4.0/patch.diff | git apply --unidiff-zero git checkout -b killerskills/1.4.0 && git commit -am "crowdstrike-falcon-fusion: Collapsed <details> block carrying instructions" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/plugins/crowdstrike-falcon-fusion/1.4.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.