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 .patchdiff --git a/data/samples.json b/data/samples.json --- a/data/samples.json +++ b/data/samples.json @@ -548,1 +548,0 @@ -…mi.com/images/docs/badges/slack.svg)](https://slack.pulumi.com) [](https://www.npmjs.com/package/@pulumi/docker-build) [](https://www.npmjs.com/package/@google/genai) []… @@ -3922,1 +3920,0 @@ -"description": "AWS credential provider that sources credentials from ~/.aws/credentials and ~/.aws/config", @@ -3966,1 +3963,0 @@ -"description": "AWS credential provider that sources credential_process from ~/.aws/credentials and ~/.aws/config", diff --git a/data/malicious.json b/data/malicious.json --- a/data/malicious.json +++ b/data/malicious.json @@ -10761,1 +10761,0 @@ -DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE
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: aagent-system: 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.9.2) 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/aagent-system/1.0.0 ## Findings with a location - `data/samples.json:1316` · URL with embedded credentials — data/samples.json:1316 · URL with embedded credentials — may be phishing or credential leaking - `data/samples.json:548` · URL with embedded credentials — data/samples.json:548 · URL with embedded credentials — may be phishing or credential leaking - `data/samples.json:3966` · References a credential file in the home directory — data/samples.json:3966 · References a credential file in the home directory - `data/samples.json:3922` · References a credential file in the home directory — data/samples.json:3922 · References a credential file in the home directory - `data/malicious.json:10761` · HTML comment carrying imperative instructions to the agent — data/malicious.json:10761 · HTML comment carrying imperative instructions to the agent · 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._
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.