← twitterapi-io@3.8.32

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

Evidence

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

Diff · removes 3 caught lines

Download .patch
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -21,1 +21,0 @@
-…er ask for or store account passwords, `auth_token`, `ct0`, `login_cookies`, or proxy credentials for a read-only workflow. --- ## Setup 1. Get API key: https://twitterapi.io…
@@ -312,1 +311,0 @@
-| Proxy error | Bad proxy format or dead proxy | Format: `http://user:pass@host:port`, use residential |
diff --git a/skills/twitterapi-io/SKILL.md b/skills/twitterapi-io/SKILL.md
--- a/skills/twitterapi-io/SKILL.md
+++ b/skills/twitterapi-io/SKILL.md
@@ -21,1 +21,0 @@
-…er ask for or store account passwords, `auth_token`, `ct0`, `login_cookies`, or proxy credentials for a read-only workflow. --- ## Setup 1. Get API key: https://twitterapi.io…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 3.8.32. 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: twitterapi-io: Credential pass-through configuration (KillerSkills verdict caution 77)

## 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 77/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/twitterapi-io/3.8.32

## Findings with a location
- `SKILL.md:21` · Credential pass-through configuration — SKILL.md:21 · Credential pass-through configuration — agent relays sensitive credentials
- `skills/twitterapi-io/SKILL.md:21` · Credential pass-through configuration — skills/twitterapi-io/SKILL.md:21 · Credential pass-through configuration — agent relays sensitive credentials
- `SKILL.md:312` · URL with embedded credentials — SKILL.md:312 · URL with embedded credentials — may be phishing or credential leaking

## Proposed change
The attached patch removes the 3 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 igorbrigadir/twitter-advanced-search --clone && cd twitter-advanced-search
curl -s https://killerskills.ai/skills/clawhub/twitterapi-io/3.8.32/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/3.8.32 && git commit -am "twitterapi-io: Credential pass-through configuration"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/clawhub/twitterapi-io/3.8.32/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.