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

Evidence

installer lure

Diff · removes 2 caught lines

Download .patch

diff --git a/.claude/hooks/validate-manifests.js b/.claude/hooks/validate-manifests.js
--- a/.claude/hooks/validate-manifests.js
+++ b/.claude/hooks/validate-manifests.js
@@ -1,1 +1,0 @@
-validate-manifests.js
diff --git a/.claude/skills/release-installer/SKILL.md b/.claude/skills/release-installer/SKILL.md
--- a/.claude/skills/release-installer/SKILL.md
+++ b/.claude/skills/release-installer/SKILL.md
@@ -30,1 +30,0 @@
-with `--registry` aimed at a local registry. An `~/.npmrc` that scopes

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.3.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: postman: installer lure (KillerSkills verdict blocked 10)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.6) and scored it **BLOCKED 10/100**. Summary: no network, touches nothing outside the project, writes no memory.

- installer lure

Full trace and findings: https://killerskills.ai/skills/plugins/postman/2.3.0

## Findings with a location
- `.claude/hooks/validate-manifests.js:1` · Payload hidden under .claude/hooks — .claude/hooks/validate-manifests.js: archive or executable placed where a reviewer would not look
- `.claude/skills/release-installer/SKILL.md:30` · References a credential file in the home directory — .claude/skills/release-installer/SKILL.md:30 · References a credential file in the home directory

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

Open the issue on GitHub (postmanlabs/postman-plugin)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork postmanlabs/postman-plugin --clone && cd postman-plugin
curl -s https://killerskills.ai/skills/plugins/postman/2.3.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/2.3.0 && git commit -am "postman: installer lure"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/plugins/postman/2.3.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.