← poltertab@1.12.0

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. 61 · Caution

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

Diff · removes 6 caught lines

Download .patch
diff --git a/mcp-server/upload-paths.js b/mcp-server/upload-paths.js
--- a/mcp-server/upload-paths.js
+++ b/mcp-server/upload-paths.js
@@ -85,1 +85,0 @@
-// bypass the check (e.g. ~/Downloads/key.pem -> ~/.ssh/id_ed25519).
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -83,1 +83,0 @@
-<summary>Or load it unpacked (developer / offline path)</summary> Use this when you are changing the extension or cannot reach the Web Store. An unpacked extens
diff --git a/site/index.html b/site/index.html
--- a/site/index.html
+++ b/site/index.html
@@ -544,1 +544,0 @@
-<summary>Developer or offline? Load the unpacked zip instead.</summary> <ol class="step-list"> <li>Download the latest <a href="https://github.com/abhinav162/po
@@ -569,1 +568,0 @@
-<summary>Can the agent read my passwords or cookies?</summary> <div class="answer"><p>It can’t open your password manager or Chrome’s cookie store. It sees what
diff --git a/test/setup.test.js b/test/setup.test.js
--- a/test/setup.test.js
+++ b/test/setup.test.js
@@ -8,1 +8,0 @@
-//   C  CLAUDE.md update    appends once, never twice
@@ -178,1 +177,0 @@
-group("C  CLAUDE.md update");

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.12.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: poltertab: References a credential file in the home directory (KillerSkills verdict caution 61)

## 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 61/100**. Summary: calls registry.npmjs.org only, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/poltertab/1.12.0

## Findings with a location
- `mcp-server/upload-paths.js:85` · References a credential file in the home directory — mcp-server/upload-paths.js:85 · References a credential file in the home directory
- `README.md:83` · Collapsed <details> block carrying instructions — README.md:83 · Collapsed <details> block carrying instructions
- `site/index.html:544` · Collapsed <details> block carrying instructions — site/index.html:544 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `test/setup.test.js:178` · Instructs the agent to modify its persistent memory or instruction files — test/setup.test.js:178 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `test/setup.test.js:8` · Instructs the agent to modify its persistent memory or instruction files — test/setup.test.js:8 · Instructs the agent to modify its persistent memory or instruction files · informational: not an instruction file
- `site/index.html:569` · Collapsed <details> block carrying instructions — site/index.html:569 · Collapsed <details> block carrying instructions · informational: not an instruction file

## Proposed change
The attached patch removes the 6 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 abhinav162/poltertab --clone && cd poltertab
curl -s https://killerskills.ai/skills/glama/poltertab/1.12.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.12.0 && git commit -am "poltertab: References a credential file in the home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/poltertab/1.12.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.