← alibabacloud-apsaradb-agent@0.2.6

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

Evidence

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

Diff · removes 2 caught lines

Download .patch
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -70,1 +70,0 @@
-Never store credentials in these variables or pass credentials through the query, metadata, command arguments, logs, or files.
@@ -110,1 +109,0 @@
-…he user asked about it or the agent recommended it. Do not confirm, collect, or relay secret values. | Parameter Name | Required/Optional | Description | Default Value | |…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.2.6. 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: alibabacloud-apsaradb-agent: Credential pass-through configuration (KillerSkills verdict caution 62)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/alibabacloud-apsaradb-agent/0.2.6

## Findings with a location
- `SKILL.md:110` · Credential pass-through configuration — SKILL.md:110 · Credential pass-through configuration — agent relays sensitive credentials
- `SKILL.md:70` · Credential pass-through configuration — SKILL.md:70 · Credential pass-through configuration — agent relays sensitive credentials

## 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._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

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.