Propose a patch

Evidence

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

diff --git a/scripts/bundle.cjs b/scripts/bundle.cjs
--- a/scripts/bundle.cjs
+++ b/scripts/bundle.cjs
@@ -2,1 +2,0 @@
-…--target=prod --no-minify",build:"pnpm run build:ppe"},internalConfig:{baseURL:"https://openclaw-innersit.sdk.access-test.clawsentry.cn",baseLogUrl:"https://console.clawsentry.cn/ai-assistant-security-dev/openclaw?loginToken="},dependencies:{"node-machine-id":"^1.1.12"},devDependencies:{"@types/node":"^25.5.0",esbuild:"^0.21.0","javascript-obfuscator":"^5.3.0",typescr…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.21. 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: senpub: URL with embedded credentials (KillerSkills verdict caution 64)

## 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 64/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/senpub/1.0.21

## Findings with a location
- `scripts/bundle.cjs:2` · URL with embedded credentials — scripts/bundle.cjs:2 · URL with embedded credentials — may be phishing or credential leaking

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