← donanimhaber-mcp@0.1.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. 60 · Caution

Evidence

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

Diff · removes 4 caught lines

Download .patch
diff --git a/tests/fixtures/article.html b/tests/fixtures/article.html
--- a/tests/fixtures/article.html
+++ b/tests/fixtures/article.html
@@ -175,1 +175,0 @@
-…pt type="application/ld+json">{"@context":"http://schema.org","@graph":[{"@id":"https://www.donanimhaber.com/aina-ai-ring-tanitildi-ekranli-akilli-yuzuk-neler-sunuyor--212567#article","author":{"@id":"https://www.donanimhaber.com/editor/erkan-calp#person","@type":"Person","na…
diff --git a/tests/fixtures/category.html b/tests/fixtures/category.html
--- a/tests/fixtures/category.html
+++ b/tests/fixtures/category.html
@@ -145,1 +145,0 @@
-….com#organization","@type":"NewsMediaOrganization","name":"DonanımHaber","url":"https://www.donanimhaber.com/","masthead":"https://www.donanimhaber.com/hakkimizda","logo":{"@type":"ImageObject","url":"https://www.donanimhaber.com/images/images/112-dh-log…
@@ -4567,1 +4566,0 @@
-…berleri"><h2 id="populer-teknolojik-gelismeler">Popüler Teknolojik Gelişmeler 👨‍💻</h2><p id="teknoloji-haberleri-paragraph-6">Kısa ve ilginç teknolojik haberle…
diff --git a/tests/fixtures/home.html b/tests/fixtures/home.html
--- a/tests/fixtures/home.html
+++ b/tests/fixtures/home.html
@@ -163,1 +163,0 @@
-… dair tüm gelişmeleri teknoloji sitesi DonanımHaber'le takip edin.","masthead":"https://www.donanimhaber.com/hakkimizda","logo":{"@type":"ImageObject","url":"https://www.donanimhaber.com/images/images/112-dh-log…

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.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: donanimhaber-mcp: 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.8.1) 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/glama/donanimhaber-mcp/0.1.0

## Findings with a location
- `tests/fixtures/article.html:175` · URL with embedded credentials — tests/fixtures/article.html:175 · URL with embedded credentials — may be phishing or credential leaking
- `tests/fixtures/category.html:4567` · Hidden zero-width characters detected — tests/fixtures/category.html:4567 · Hidden zero-width characters detected — may conceal content
- `tests/fixtures/home.html:163` · URL with embedded credentials — tests/fixtures/home.html:163 · URL with embedded credentials — may be phishing or credential leaking
- `tests/fixtures/category.html:145` · URL with embedded credentials — tests/fixtures/category.html:145 · URL with embedded credentials — may be phishing or credential leaking

## Proposed change
The attached patch removes the 4 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 mohammad-abbasi-sh/donanimhaber-mcp --clone && cd donanimhaber-mcp
curl -s https://killerskills.ai/skills/glama/donanimhaber-mcp/0.1.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.1.0 && git commit -am "donanimhaber-mcp: URL with embedded credentials"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/donanimhaber-mcp/0.1.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.