← adrails@0.14.4

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

Evidence

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

Diff · removes 4 caught lines

Download .patch
diff --git a/adsops/oai_builder.py b/adsops/oai_builder.py
--- a/adsops/oai_builder.py
+++ b/adsops/oai_builder.py
@@ -527,1 +527,0 @@
-ok(refused(lambda: draft(brief(landing_url="https://user:[email protected]/x"), now=fixed_now)))
diff --git a/adsops/content/facts.py b/adsops/content/facts.py
--- a/adsops/content/facts.py
+++ b/adsops/content/facts.py
@@ -818,1 +818,0 @@
-{"site": "https://user:[email protected]/", "facts_file": "F"})),
diff --git a/adsops/seo/fetcher.py b/adsops/seo/fetcher.py
--- a/adsops/seo/fetcher.py
+++ b/adsops/seo/fetcher.py
@@ -206,1 +206,0 @@
-("https://u:[email protected]/", pub), ("https://a.example/\r\nX: y", pub), ("http://10.0.0.1/", pub),
diff --git a/adsops/seo/render.py b/adsops/seo/render.py
--- a/adsops/seo/render.py
+++ b/adsops/seo/render.py
@@ -466,1 +466,0 @@
-ck(request_allowed("https://u:[email protected]/") is False, "credentials refused")

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

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/adrails/0.14.4

## Findings with a location
- `adsops/oai_builder.py:527` · URL with embedded credentials — adsops/oai_builder.py:527 · URL with embedded credentials — may be phishing or credential leaking
- `adsops/content/facts.py:818` · URL with embedded credentials — adsops/content/facts.py:818 · URL with embedded credentials — may be phishing or credential leaking
- `adsops/seo/fetcher.py:206` · URL with embedded credentials — adsops/seo/fetcher.py:206 · URL with embedded credentials — may be phishing or credential leaking
- `adsops/seo/render.py:466` · URL with embedded credentials — adsops/seo/render.py:466 · 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 antonioac1/adrails --clone && cd adrails
curl -s https://killerskills.ai/skills/pypi/adrails/0.14.4/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.14.4 && git commit -am "adrails: URL with embedded credentials"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/adrails/0.14.4/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.