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. 24 · Blocked

Evidence

Contacted fd12:ea5f:789c:1:d000:2b:95f6:3c3a, 10.246.60.58, www.skills.sh: not declared and not needed for the documented job.
Read ~/work/acme-api/.npmrc, ~/.npmrc in the decoy home directory.
A credential file was read and an undeclared host contacted in the same run.

Diff

No finding carries a file and line, so there is no mechanical diff; the issue body below carries the evidence and the fix is a declaration or a removal the maintainer chooses.

Issue / PR body

Title: super-stock-trading: Contacted fd12:ea5f:789c:1:d000:2b:95f6:3c3a, 10.246.60.58, www.skills.sh: not declared and not needed for the documented job (KillerSkills verdict blocked 24)

## 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 **BLOCKED 24/100**. Summary: reads credential files, sends data to fd12:ea5f:789c:1:d000:2b:95f6:3c3a, 10.246.60.58, www.skills.sh.

- Contacted fd12:ea5f:789c:1:d000:2b:95f6:3c3a, 10.246.60.58, www.skills.sh: not declared and not needed for the documented job.
- Read ~/work/acme-api/.npmrc, ~/.npmrc in the decoy home directory.
- A credential file was read and an undeclared host contacted in the same run.

Full trace and findings: https://killerskills.ai/skills/clawhub/super-stock-trading/1.1.0

## Findings with a location
- No finding carries a file and line; the evidence above comes from the run itself.

## Proposed change
Declare the behavior if it is intended (hosts under `permissions.network`, a line in the README), or remove it. The next crawl re-scores the new version automatically.

## 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.