bcrypt 5.0.0
- Source
- https://github.com/pyca/bcrypt
- Tag scanned
5.0.0- Compared with
4.3.0(0 signals introduced since)- Files
- 8 scanned, 6 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 22 info
- Scan time
- 14.5 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 22 of 22 warn and critical signals; 22 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 05:42
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
dismissed Binary test vector bytes in a bcrypt test file.
Reasoning
The bytes literal sits in a bcrypt test file, where binary hash and salt test vectors are expected. The escapes are fixed-length byte values with no decoding or execution path, so the payload-shape heuristic is matching legitimate test data.
-
dismissed Binary test vector bytes in a bcrypt test file.
Reasoning
This is another binary byte literal in the bcrypt test suite, consistent with known-answer test vectors. Nothing in the snippet decodes, executes, or transmits the bytes.
-
b, b b, ],dismissed Fixed binary salt or hash fixture in a test case list.Reasoning
The literal is a 16-byte salt or hash fixture in a list of bcrypt test cases. The payload-shape finding comes from the many \xNN escapes, which is normal for raw binary test data.
-
b, b b, ],dismissed Hex-escaped binary test fixture.Reasoning
Hex escapes representing raw bytes are the expected way to write binary test fixtures in Python. The entropy is typical of random-looking hash output, and the context is a test file.
-
b b, ],dismissed Hex-escaped binary test fixture continuation.Reasoning
This is a continuation of the same binary test vector list. The raw pass flags ordinary hex escapes in a test fixture, a known false-positive pattern.
-
b, b, ],dismissed Hex-escaped binary test fixture.Reasoning
Binary test vectors appear here as well, in the same expected-output structure of a bcrypt test. No decoding or execution is present.
-
b, b, ],dismissed Hex-escaped binary test fixture.Reasoning
This is a 16-byte binary fixture in a list of test inputs and expected outputs. The raw match reflects hex-escaped bytes, not obfuscation.
-
b, b b, ],dismissed Binary salt and hash fixture in a bcrypt test.Reasoning
The literal is a salt with a null byte followed by binary hash bytes, a standard form for bcrypt known-answer tests. The payload-shape signal comes only from the escape density.
-
b, b b, ],dismissed Hex-escaped binary test fixture.Reasoning
Hex-escaped bytes in a test fixture are expected here. The raw pass flags a common false-positive pattern in binary test data.
-
b b, ],dismissed Hex-escaped binary test fixture continuation.Reasoning
This continues the same binary fixture list in the bcrypt test file. The bytes are static test data with no runtime use.
-
b, b, ],dismissed Hex-escaped binary test fixture with a salt.Reasoning
The snippet is a binary test vector with a salt and expected hash, a common test pattern in cryptographic libraries. The raw entropy reflects random-looking hash output.
-
b, b, ],dismissed Hex-escaped binary test fixture.Reasoning
This is another binary test vector in the bcrypt test suite. The escapes encode expected output bytes, with no dynamic execution or exfiltration.
-
b, b b bdismissed Large binary test vector in a bcrypt test file.Reasoning
A 64-byte binary literal built from concatenated escapes in a bcrypt test file matches known-answer test data. The payload-shape rule fires on the byte density, not on any malicious behavior.
-
b, b b blikely benign Binary test-vector byte literals in a bcrypt unit test file.Reasoning
The file is a bcrypt test suite; the byte literals are known test vectors (salts, hashes, keys) in a parametrized list. Hex escape runs are the normal way to express binary test data in Python tests.
-
b, b, ],likely benign Binary test-vector bytes inside a bcrypt test parameter list.Reasoning
Same bcrypt test-vector table of raw byte values used as expected inputs or outputs; the pattern is legitimate test data encoding.
-
b, b, ],likely benign Binary test vector in bcrypt tests.Reasoning
Test vector bytes in a bcrypt test file, consistent with a known-answer test table; no execution or decoding logic is present.
-
8, b, b, b,likely benign Binary known-answer test data in bcrypt tests.Reasoning
Repeated rows of binary expected values in a bcrypt known-answer test table; benign test data.
-
b, b, b, ],likely benign Binary known-answer test data in bcrypt tests.Reasoning
Continuation of the same bcrypt test vector table; benign.
-
b, b, ],likely benign Binary known-answer test data in bcrypt tests.Reasoning
Continuation of the same bcrypt test vector table; benign.
-
8, b, b, blikely benign Large binary test-vector table in bcrypt tests.Reasoning
Large block of bcrypt test vectors (e.g., the eksblowfish/bcrypt-pbkdf style known answers) in a test file; hex escapes are the expected representation of binary test inputs.
-
b, b b blikely benign Concatenated bytes literal of binary test vectors in bcrypt tests.Reasoning
The AST pass flags a concatenated bytes literal of 256 escapes, which is the same test-vector table. Its shape matches binary data, but it is a test fixture in a crypto library test suite, not a dropper or executed payload.
-
b, b, ], ],likely benign Binary test vector bytes in bcrypt tests.Reasoning
Binary test data rows in a bcrypt test table; the raw-pass escape-run heuristic fires on expected test vectors only.
Reproduce This Scan
Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
&&