← huo15-wecom-plugin@2.9.5

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

Evidence

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

Diff · removes 2 caught lines

Download .patch
diff --git a/scripts/test-proxy.ts b/scripts/test-proxy.ts
--- a/scripts/test-proxy.ts
+++ b/scripts/test-proxy.ts
@@ -24,1 +24,0 @@
-proxyUrl = `http://${encodeURIComponent(user)}:${encodeURIComponent(pass)}@${host}:${port}`;
diff --git a/src/onboarding.ts b/src/onboarding.ts
--- a/src/onboarding.ts
+++ b/src/onboarding.ts
@@ -311,1 +311,0 @@
-"👨‍💻 作者: YanHaidao (微信: YanHaidao)",

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

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.9.2) and scored it **CAUTION 60/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/huo15-wecom-plugin/2.9.5

## Findings with a location
- `scripts/test-proxy.ts:24` · URL with embedded credentials — scripts/test-proxy.ts:24 · URL with embedded credentials — may be phishing or credential leaking
- `src/onboarding.ts:311` · Hidden zero-width characters detected — src/onboarding.ts:311 · Hidden zero-width characters detected — may conceal content

## 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._
# or from a terminal, under your own account:
gh repo fork YanHaidao/wecom --clone && cd wecom
curl -s https://killerskills.ai/skills/clawhub/huo15-wecom-plugin/2.9.5/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/2.9.5 && git commit -am "huo15-wecom-plugin: URL with embedded credentials"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/huo15-wecom-plugin/2.9.5/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.