dnspython 2.9.0
- Source
- https://github.com/rthalley/dnspython
- Artifact scanned
dnspython-2.9.0-py3-none-any.whl- Compared with
dnspython-2.8.0-py3-none-any.whl(0 signals introduced since)- Files
- 161 scanned, 4 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 2 info
- Scan time
- 3.2 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 1 of 1 warn and critical signal; 1 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 05:36
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
# # r'\150\151\152\153\154\155\156\157\158\159' # # then it's still "all ASCII" even though the domain name has -
= =likely benign TSIG key handling in the dnspython library, where a base64-encoded secret is decoded and stored.Reasoning
The snippet is ordinary dnspython TSIG setup: a string secret is base64-decoded with base64.decodebytes and stored on the object, which is standard key handling. The flagged decompress() call is not visible in the snippet, and the file is a DNS library with no sign of a hidden payload being run. The finding looks like a broad import-plus-method heuristic firing on a legitimate module.
Reproduce This Scan
Run disclude locally to verify. These commands scan the published file; the "new in this release" marks come from comparing it with the previous release's file, which they don't repeat. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
|