← nifimcp@0.1.0rc1
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. 76 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 14 caught lines
Download .patchdiff --git a/src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json b/src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json --- a/src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json +++ b/src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json @@ -85,1 +85,0 @@ -"previousValue": "https://ingest-user:[email protected]/feed", @@ -86,1 +85,0 @@ -"value": "https://ingest-user:[email protected]/feed" @@ -177,1 +175,0 @@ -"previousValue": "https://ingest-user:[email protected]/feed", @@ -178,1 +175,0 @@ -"value": "https://ingest-user:[email protected]/feed" @@ -269,1 +265,0 @@ -"previousValue": "https://ingest-user:[email protected]/feed", diff --git a/src/nifimcp/demo_data/telemetry-intake/provenance-trace.json b/src/nifimcp/demo_data/telemetry-intake/provenance-trace.json --- a/src/nifimcp/demo_data/telemetry-intake/provenance-trace.json +++ b/src/nifimcp/demo_data/telemetry-intake/provenance-trace.json @@ -81,1 +81,0 @@ -"previousValue": "https://ingest-user:[email protected]/feed", @@ -82,1 +81,0 @@ -"value": "https://ingest-user:[email protected]/feed" @@ -174,1 +172,0 @@ -"previousValue": "https://ingest-user:[email protected]/feed", @@ -175,1 +172,0 @@ -"value": "https://ingest-user:[email protected]/feed" @@ -266,1 +262,0 @@ -"previousValue": "https://ingest-user:[email protected]/feed", diff --git a/scripts/build_demo_bundle.py b/scripts/build_demo_bundle.py --- a/scripts/build_demo_bundle.py +++ b/scripts/build_demo_bundle.py @@ -113,1 +113,0 @@ -"upstream.url": "https://ingest-user:[email protected]/feed", diff --git a/src/nifimcp/demo_data/telemetry-intake/flow-definition.json b/src/nifimcp/demo_data/telemetry-intake/flow-definition.json --- a/src/nifimcp/demo_data/telemetry-intake/flow-definition.json +++ b/src/nifimcp/demo_data/telemetry-intake/flow-definition.json @@ -1,1 +1,0 @@ -…d.owner":"telemetry-team","Cache Value Lookup Cache Size":"100","upstream.url":"https://ingest-user:[email protected]/feed","Stateful Variables Initial Value":null},"proper… diff --git a/src/nifimcp/core/jsonsafe.py b/src/nifimcp/core/jsonsafe.py --- a/src/nifimcp/core/jsonsafe.py +++ b/src/nifimcp/core/jsonsafe.py @@ -82,1 +82,0 @@ -if text.startswith(""): diff --git a/src/nifimcp/demo_data/telemetry-intake-candidate.json b/src/nifimcp/demo_data/telemetry-intake-candidate.json --- a/src/nifimcp/demo_data/telemetry-intake-candidate.json +++ b/src/nifimcp/demo_data/telemetry-intake-candidate.json @@ -1,1 +1,0 @@ -…d.owner":"telemetry-team","Cache Value Lookup Cache Size":"100","upstream.url":"https://ingest-user:[email protected]/feed","Stateful Variables Initial Value":null},"proper…
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.0rc1. 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: nifimcp: URL with embedded credentials (KillerSkills verdict caution 76)
## 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 76/100**. Summary: no network, touches nothing outside the project, writes no memory. - See the findings below. Full trace and findings: https://killerskills.ai/skills/glama/nifimcp/0.1.0rc1 ## Findings with a location - `src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json:86` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json:86 · URL with embedded credentials — may be phishing or credential leaking - `src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:81` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:81 · URL with embedded credentials — may be phishing or credential leaking - `src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json:177` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json:177 · URL with embedded credentials — may be phishing or credential leaking - `src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json:85` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake/provenance-unmatched.json:85 · URL with embedded credentials — may be phishing or credential leaking - `src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:266` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:266 · URL with embedded credentials — may be phishing or credential leaking - `src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:82` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:82 · URL with embedded credentials — may be phishing or credential leaking - `scripts/build_demo_bundle.py:113` · URL with embedded credentials — scripts/build_demo_bundle.py:113 · URL with embedded credentials — may be phishing or credential leaking - `src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:175` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:175 · URL with embedded credentials — may be phishing or credential leaking - `src/nifimcp/demo_data/telemetry-intake/flow-definition.json:1` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake/flow-definition.json:1 · URL with embedded credentials — may be phishing or credential leaking - `src/nifimcp/core/jsonsafe.py:82` · Hidden zero-width characters detected — src/nifimcp/core/jsonsafe.py:82 · Hidden zero-width characters detected — may conceal content - `src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:174` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake/provenance-trace.json:174 · URL with embedded credentials — may be phishing or credential leaking - `src/nifimcp/demo_data/telemetry-intake-candidate.json:1` · URL with embedded credentials — src/nifimcp/demo_data/telemetry-intake-candidate.json:1 · URL with embedded credentials — may be phishing or credential leaking ## Proposed change The attached patch removes the 14 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 nifimcp/nifimcp --clone && cd nifimcp curl -s https://killerskills.ai/skills/glama/nifimcp/0.1.0rc1/patch.diff | git apply --unidiff-zero git checkout -b killerskills/0.1.0rc1 && git commit -am "nifimcp: URL with embedded credentials" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/nifimcp/0.1.0rc1/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.