Propose a patch

Evidence

• Contacted release-assets.githubusercontent.com: not declared and not needed for the documented job.

diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -84,1 +84,0 @@
-<summary><b>With Node.js (no install step): <code>npx</code></b></summary> ```bash npx -y nullwire-mcp install --client all ``` Nothing to download by hand: the
@@ -93,1 +92,0 @@
-<summary><b>macOS, Linux and Termux: install script</b></summary> ```bash curl -fsSL https://raw.githubusercontent.com/VoxNode-ux/nullwire-mcp/main/scripts/inst
@@ -102,1 +100,0 @@
-<summary><b>Windows: install script</b></summary> ```powershell irm https://raw.githubusercontent.com/VoxNode-ux/nullwire-mcp/main/scripts/install.ps1 | iex nul
@@ -112,1 +109,0 @@
-<summary><b>Short install URL (GitHub Pages)</b></summary> ```bash curl -fsSL https://voxnode-ux.github.io/nullwire-mcp/install.sh | sh -s -- --setup ``` ```pow
@@ -124,1 +120,0 @@
-<summary><b>Linux packages and distributions</b></summary> ```bash # Debian, Ubuntu: download the .deb from the release page, then sudo apt install ./nullwire-m
@@ -151,1 +146,0 @@
-<summary><b>Python, GitHub CLI, mise and asdf</b></summary> ```bash pipx run nullwire-mcp install --client all # or: pip install nullwire-mcp gh extension insta
diff --git a/npm/README.md b/npm/README.md
--- a/npm/README.md
+++ b/npm/README.md
@@ -61,1 +61,0 @@
-<summary><b>With Node.js (no install step): <code>npx</code></b></summary> ```bash npx -y nullwire-mcp install --client all ``` Nothing to download by hand: the
@@ -70,1 +69,0 @@
-<summary><b>macOS, Linux and Termux: install script</b></summary> ```bash curl -fsSL https://raw.githubusercontent.com/VoxNode-ux/nullwire-mcp/main/scripts/inst
@@ -79,1 +77,0 @@
-<summary><b>Windows: install script</b></summary> ```powershell irm https://raw.githubusercontent.com/VoxNode-ux/nullwire-mcp/main/scripts/install.ps1 | iex nul
@@ -89,1 +86,0 @@
-<summary><b>Short install URL (GitHub Pages)</b></summary> ```bash curl -fsSL https://voxnode-ux.github.io/nullwire-mcp/install.sh | sh -s -- --setup ``` ```pow
@@ -101,1 +97,0 @@
-<summary><b>Linux packages and distributions</b></summary> ```bash # Debian, Ubuntu: download the .deb from the release page, then sudo apt install ./nullwire-m
@@ -128,1 +123,0 @@
-<summary><b>Python, GitHub CLI, mise and asdf</b></summary> ```bash pipx run nullwire-mcp install --client all # or: pip install nullwire-mcp gh extension insta
diff --git a/.github/workflows/distribute.yml b/.github/workflows/distribute.yml
--- a/.github/workflows/distribute.yml
+++ b/.github/workflows/distribute.yml
@@ -54,1 +54,0 @@
-git clone --depth 1 "https://x-access-token:${TAP_TOKEN}@github.com/VoxNode-ux/$1.git" "$dir"
diff --git a/internal/app/main_test.go b/internal/app/main_test.go
--- a/internal/app/main_test.go
+++ b/internal/app/main_test.go
@@ -208,1 +208,0 @@
-"userinfo": {"http://admin:[email protected]/path", "hunter2pass"},

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of r1. 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: nullwire-mcp: Contacted release-assets.githubusercontent.com: not declared and not needed for the documented job (KillerSkills verdict blocked 39)

## What the honeypot observed
KillerSkills ran **nullwire-mcp@r1** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **BLOCKED 39/100**. Summary: sends data to release-assets.githubusercontent.com.

- Contacted release-assets.githubusercontent.com: not declared and not needed for the documented job.

Full trace and findings: https://killerskills.ai/skills/glama/nullwire-mcp/r1

## Findings with a location
- `README.md:93` · Collapsed <details> block carrying instructions — README.md:93 · Collapsed <details> block carrying instructions
- `README.md:102` · Collapsed <details> block carrying instructions — README.md:102 · Collapsed <details> block carrying instructions
- `README.md:84` · Collapsed <details> block carrying instructions — README.md:84 · Collapsed <details> block carrying instructions
- `README.md:151` · Collapsed <details> block carrying instructions — README.md:151 · Collapsed <details> block carrying instructions
- `README.md:112` · Collapsed <details> block carrying instructions — README.md:112 · Collapsed <details> block carrying instructions
- `README.md:124` · Collapsed <details> block carrying instructions — README.md:124 · Collapsed <details> block carrying instructions
- `npm/README.md:79` · Collapsed <details> block carrying instructions — npm/README.md:79 · Collapsed <details> block carrying instructions
- `npm/README.md:61` · Collapsed <details> block carrying instructions — npm/README.md:61 · Collapsed <details> block carrying instructions
- `npm/README.md:70` · Collapsed <details> block carrying instructions — npm/README.md:70 · Collapsed <details> block carrying instructions
- `.github/workflows/distribute.yml:54` · URL with embedded credentials — .github/workflows/distribute.yml:54 · URL with embedded credentials — may be phishing or credential leaking
- `npm/README.md:101` · Collapsed <details> block carrying instructions — npm/README.md:101 · Collapsed <details> block carrying instructions
- `npm/README.md:89` · Collapsed <details> block carrying instructions — npm/README.md:89 · Collapsed <details> block carrying instructions

## Proposed change
The attached patch removes the 14 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._