httptools 0.9.0
- Source
- https://github.com/MagicStack/httptools
- Artifact scanned
httptools-0.9.0.tar.gz- Compared with
httptools-0.8.0.tar.gz(124 signals introduced since)- Files
- 27 scanned, 16 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 40 warn · 98 info
- Scan time
- 89.0 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): the 100 most severe of 130 warn and critical signals (100 with a verdict); 90 demoted to info. The rest are unreviewed.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 06:00
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
214\025u\003\207b\214\334 ODHq\013x\0310\302a\327a\202\031\214\263\020\300\036\034\206\270\024\235\243<&\247\242c\272\0311o\337\241vh\340\316t\350\000\033\371\335\221O\206\314\017\374\365\375\037 \341\223<\277\343yn\320\005O\263\253\300\noc\231\215\223\027\014\343\271\021H\324\300\335\312\214\361I8\204\357\t\224\017\27likely benign A long octal-escaped byte-string literal in the httptools URL parser C source.Reasoning
Raw-pass octal-escape match on a long byte-string literal in a C parser source. The bytes look high-entropy and binary, which could be an embedded blob, but the raw pass has a high false-positive rate and the snippet shows only data, with no decoding, execution or network call. Likely a generated table or test vector in a parser library.
-
24\235\243<&\247\242c\272\0311o\337\241vh\340\316t\350\000\033\371\335\221O\206\314\017\374\365\375\037 \341\223<\277\343yn\320\005O\263\253\300\noc\231\215\223\027\014\343\271\021H\324\300\335\312\214\361I8\204\357\t\224\017\277\244C\363\212z\030\023\316\263\255\005\3234\223\275@8\331\332)\"\300\343\023\226\207\360\24likely benign Another octal-escaped byte run within the same string literal in url_parser.c.Reasoning
Same line and literal as the other findings in this group; a shorter run of octal escapes inside the same binary-looking data. The raw pass flags it without any executable context, so it reads as data in a parser source.
-
\0311o\337\241vh\340\316t\350\000\033\371\335\221O\206\314\017\374\365\375\037 \341\223<\277\343yn\320\005O\263\253\300\noc\231\215\223\027\014\343\271\021H\324\300\335\312\214\361I8\204\357\t\224\017\277\244C\363\212z\030\023\316\263\255\005\3234\223\275@8\331\332)\"\300\343\023\226\207\360\245\033\360\334\"\210\237\2likely benign A further octal-escape run inside the same byte literal in url_parser.c.Reasoning
Part of the same long escaped byte sequence on line 6357. Only data is shown, with no code that uses it, so the raw signal is most plausibly a generated table or constant data.
-
5\037 \341\223<\277\343yn\320\005O\263\253\300\noc\231\215\223\027\014\343\271\021H\324\300\335\312\214\361I8\204\357\t\224\017\277\244C\363\212z\030\023\316\263\255\005\3234\223\275@8\331\332)\"\300\343\023\226\207\360\245\033\360\334\"\210\237\257\300\031^\270\365\003\302\013s\301\320\271\354\226\006:\314\024Hs\031J\likely benign Octal escape run within the long byte literal in httptools url_parser.c.Reasoning
Raw-pass match inside the same binary-looking literal. The snippet contains only escaped bytes with no decoding or execution, and the raw pass is known to be noisy.
-
O\263\253\300\noc\231\215\223\027\014\343\271\021H\324\300\335\312\214\361I8\204\357\t\224\017\277\244C\363\212z\030\023\316\263\255\005\3234\223\275@8\331\332)\"\300\343\023\226\207\360\245\033\360\334\"\210\237\257\300\031^\270\365\003\302\013s\301\320\271\354\226\006:\314\024Hs\031J\257\035\3707\351\003\027\300*f\03likely benign Octal-escape run in the same binary constant in url_parser.c.Reasoning
Another run of escapes from the same literal. Nothing in the snippet shows a call that consumes the bytes, so this is most likely embedded constant data rather than a dropper.
-
\312\214\361I8\204\357\t\224\017\277\244C\363\212z\030\023\316\263\255\005\3234\223\275@8\331\332)\"\300\343\023\226\207\360\245\033\360\334\"\210\237\257\300\031^\270\365\003\302\013s\301\320\271\354\226\006:\314\024Hs\031J\257\035\3707\351\003\027\300*f\032;R\311\000\232\212\022\035\n\207\311\306\322\240\333\201\207]likely benign Octal escape run in the httptools url_parser.c byte literal.Reasoning
Raw signal from the same long escaped literal. The snippet shows only data and no executable context, consistent with a benign generated table in a parser library.
-
\030\023\316\263\255\005\3234\223\275@8\331\332)\"\300\343\023\226\207\360\245\033\360\334\"\210\237\257\300\031^\270\365\003\302\013s\301\320\271\354\226\006:\314\024Hs\031J\257\035\3707\351\003\027\300*f\032;R\311\000\232\212\022\035\n\207\311\306\322\240\333\201\207]b\210\303A\303\220\264Q\304\241m\342\374>/\277\047likely benign Octal escape run in the same literal inside url_parser.c.Reasoning
Part of the same literal on line 6357. The snippet contains no code that decodes or runs the data, so the finding rests only on the byte-pattern heuristic.
-
60\334\"\210\237\257\300\031^\270\365\003\302\013s\301\320\271\354\226\006:\314\024Hs\031J\257\035\3707\351\003\027\300*f\032;R\311\000\232\212\022\035\n\207\311\306\322\240\333\201\207]b\210\303A\303\220\264Q\304\241m\342\374>/\277\047\225OL1\005\331\370\234\353\223UC0C}\315\205\364\274\\\317*\232\013n6^=\331\313&\256likely benign Escaped byte run in the same url_parser.c literal.Reasoning
Raw-pass finding on the same escaped byte sequence. Without a consumer or execution context in the snippet, the match fits constant data in a C parser, and the raw pass over-flags such data.
-
14\024Hs\031J\257\035\3707\351\003\027\300*f\032;R\311\000\232\212\022\035\n\207\311\306\322\240\333\201\207]b\210\303A\303\220\264Q\304\241m\342\374>/\277\047\225OL1\005\331\370\234\353\223UC0C}\315\205\364\274\\\317*\232\013n6^=\331\313&\256\027b83\2371E5\274\320!\363\031\325\224likely benign Octal escape run from the long byte literal in httptools url_parser.c.Reasoning
Same literal and pass as the rest of the group. The snippet shows only binary-looking data and no decoding, spawning or network activity, so the signal is most consistent with a benign data table.
-
\351\003\027\300*f\032;R\311\000\232\212\022\035\n\207\311\306\322\240\333\201\207]b\210\303A\303\220\264Q\304\241m\342\374>/\277\047\225OL1\005\331\370\234\353\223UC0C}\315\205\364\274\\\317*\232\013n6^=\331\313&\256\027b83\2371E5\274\320!\363\031\325\224\330\274\3likely benign Octal escape run in the same byte literal in url_parser.c.Reasoning
Last finding in the group, from the same literal. Only escaped bytes are shown with no executable use, so the heuristic match alone does not indicate malicious intent.
-
377\030\220q\330\010\025\220Q\337\330\010\026\220a\000\007\330\010\367\031\230\021\000\002\330\010\030\230\377\001\360\010\000\005\016\210Q\377\330\030$\240A\240Q\330\377\013 \240\001\240\021\340\004~0\000\220u\230A\230X\021\000\377\004\005\330\010\013\2106\220\367\025\220b+\002\r\023\320\022\377+\2501\330\020\021\330% -
\013 \240\001\240\021\340\004~0\000\220u\230A\230X\021\000\377\004\005\330\010\013\2106\220\367\025\220b+\002\r\023\320\022\377+\2501\330\020\021\330%\377,\250A\250V\2606\270\377\021\340\010\023\2207\230&\333\240\001q\000\320\025\034\000\250J\377\260f\270F\300#\300Q\375\340;\0004\210s\220!\330\377\014\017\210v\220 -
022\377+\2501\330\020\021\330%\377,\250A\250V\2606\270\377\021\340\010\023\2207\230&\333\240\001q\000\320\025\034\000\250J\377\260f\270F\300#\300Q\375\340;\0004\210s\220!\330\377\014\017\210v\220 -
14\000\025\220V\377\230;""\240a\240|\260;\377\270a\330\020\031\230\030\240\377\021\240$\240c\250\021\250\373!\340\"\027I\270Q\330\020\3762\0079\270A\330\020\027\220\177x\230q\240\004\240C[\000}\001+\016\027\220v\230Q\005J\322\300\007J\267\001\300\007:\231\001\030\230\375\010\324 \024\240S\250\001\250\335\021\257\030M\3 -
\014\260K\270\014\000\025\220V\377\230;""\240a\240|\260;\377\270a\330\020\031\230\030\240\377\021\240$\240c\250\021\250\373!\340\"\027I\270Q\330\020\3762\0079\270A\330\020\027\220\177x\230q\240\004\240C[\000}\001+\016\027\220v\230Q\005J\322\300\007J\267\001\300\007:\231\001\030\230\375\010\324 \024\240S\250\001\250\335 -
6\027\220v\230Q\005J\322\300\007J\267\001\300\007:\231\001\030\230\375\010\324 \024\240S\250\001\250\335\021\257\030M\300\021\276\t=\300\377\001\330\020\033\2308\2401\377\240D\250\003\2501\250A\376\0009\340\014\023\2203\220a\376\226 v\240V\2506\260\027\327\270\n\300\324 \022\310B\320,\377>\270g\300Q\300a\340\376\221a\2 -
001\300\007:\231\001\030\230\375\010\324 \024\240S\250\001\250\335\021\257\030M\300\021\276\t=\300\377\001\330\020\033\2308\2401\377\240D\250\003\2501\250A\376\0009\340\014\023\2203\220a\376\226 v\240V\2506\260\027\327\270\n\300\324 \022\310B\320,\377>\270g\300Q\300a\340\376\221a\230\021\230!\330\010\022\017\220!\2201" -
4\240S\250\001\250\335\021\257\030M\300\021\276\t=\300\377\001\330\020\033\2308\2401\377\240D\250\003\2501\250A\376\0009\340\014\023\2203\220a\376\226 v\240V\2506\260\027\327\270\n\300\324 \022\310B\320,\377>\270g\300Q\300a\340\376\221a\230\021\230!\330\010\022\017\220!\2201"; -
static const char bytes = "(tree fragment).<URL schema: {!r}, host: {!r}, port: {!r}, path: {!r}, query: {!r}, fragment: {!r}, userinfo: {!r}>?Note that Cython is deliberately stricter than PEP-484 and rejects subclasses of builtin types. If you need to pass subclasses then set the \047annotation_typing\047 directive -
330\010\026\220a\330\010\025\220Q\330\010\026\220a\330\010\031\230\021\330\010\031\230\021\330\010\030\230\001\360\010\000\005\016\210Q\330\030$\240A\240Q\330\013 \240\001\240\021\340\004\026\220a\220u\230A\230X\240Q\330\004\005\330\010\013\2106\220\025\220b\230\001\360\010\000\r\023\320\022+\2501\330\020\021\330%,\250 -
0\010\000\005\016\210Q\330\030$\240A\240Q\330\013 \240\001\240\021\340\004\026\220a\220u\230A\230X\240Q\330\004\005\330\010\013\2106\220\025\220b\230\001\360\010\000\r\023\320\022+\2501\330\020\021\330%,\250A\250V\2606\270\021\340\010\023\2207\230&\240\001\330\010\025\320\025+\2501\250J\260f\270F\300#\300Q\340\010\013\ -
0\001\240\021\340\004\026\220a\220u\230A\230X\240Q\330\004\005\330\010\013\2106\220\025\220b\230\001\360\010\000\r\023\320\022+\2501\330\020\021\330%,\250A\250V\2606\270\021\340\010\023\2207\230&\240\001\330\010\025\320\025+\2501\250J\260f\270F\300#\300Q\340\010\013\2104\210s\220!\330\014\017\210v\220 -
023\320\022+\2501\330\020\021\330%,\250A\250V\2606\270\021\340\010\023\2207\230&\240\001\330\010\025\320\025+\2501\250J\260f\270F\300#\300Q\340\010\013\2104\210s\220!\330\014\017\210v\220 -
330%,\250A\250V\2606\270\021\340\010\023\2207\230&\240\001\330\010\025\320\025+\2501\250J\260f\270F\300#\300Q\340\010\013\2104\210s\220!\330\014\017\210v\220 -
60K\270q\330\020\025\220V\230;\240a\240|\260;\270a\330\020\031\230\030\240\021\240$\240c\250\021\250!\340\014\017\210v\220 -
\2609\270A\330\020\027\220x\230q\240\004\240C\240q\250\001\340\014\017\210v\220 -
\2609\270A\330\020\027\220x\230q\240\004\240C\240q\250\001\340\014\017\210v\220 -
60J\270a\330\020\025\220V\230;\240a\240|\260:\270Q\330\020\030\230\010\240\001\240\024\240S\250\001\250\021\340\014\017\210v\220 -
260:\270Q\330\020\030\230\010\240\001\240\024\240S\250\001\250\021\340\014\017\210v\220 -
\240Z\250q\330\020\026\220f\230K\240q\250\014\260M\300\021\330\020\025\220V\230;\240a\240|\260=\300\001\330\020\033\2308\2401\240D\250\003\2501\250A\340\014\017\210v\220 -
\260M\300\021\330\020\025\220V\230;\240a\240|\260=\300\001\330\020\033\2308\2401\240D\250\003\2501\250A\340\014\017\210v\220 -
\240Z\250q\330\020\026\220f\230K\240q\250\014\260M\300\021\330\020\025\220V\230;\240a\240|\260=\300\001\330\020\033\2308\2401\240D\250\003\2501\250A\340\014\023\2203\220a\220x\230v\240V\2506\260\027\270\n\300!\340\014\022\320\022+\2501\320,>\270g\300Q\300a\340\010\030\230\001\230\021\230!\330\010\022\220!\2201"; -
\260M\300\021\330\020\025\220V\230;\240a\240|\260=\300\001\330\020\033\2308\2401\240D\250\003\2501\250A\340\014\023\2203\220a\220x\230v\240V\2506\260\027\270\n\300!\340\014\022\320\022+\2501\320,>\270g\300Q\300a\340\010\030\230\001\230\021\230!\330\010\022\220!\2201"; -
-
-
-
-
"p3p: policyref=\"http://www.amazon.com/w3c/p3p.xml\",CP=\"CAO DSP LAW CUR ADM IVAo IVDo CONo OTPo OUR DELi PUBi OTRi BUS PHY ONL UNI PUR FIN COM NAV INT DEM CNT STA HEA PRE LOC GOV OTC \"\r\n" "x-amz-id-2: STN69VZxIFSz9YJLbz1GDbxpbjG6Qjmmq5E3DxRhOUw+Et0p4hr7c/Q8qNcx4oAD\r\n" -
, , -
"X-SSL-Nonsense: -----BEGIN CERTIFICATE-----\r\n" "\tMIIFbTCCBFWgAwIBAgICH4cwDQYJKoZIhvcNAQEFBQAwcDELMAkGA1UEBhMCVUsx\r\n" "\tETAPBgNVBAoTCGVTY2llbmNlMRIwEAYDVQQLEwlBdXRob3JpdHkxCzAJBgNVBAMT\r\n" "\tAkNBMS0wKwYJKoZIhvcNAQkBFh5jYS1vcGVyYXRvckBncmlkLXN1cHBvcnQuYWMu\r\n" -
const str_length_index = -
21h\221\nM\370\020\252\252j4\336}\327\336\262\236Y\357\314\232\030\204\3041G\037\367\270\307=\356\321G\216=\372\270\307\374\004~B\337\331\315\2567\266\261\354\314\314\363\274_\363\314\314\233u\345\001\020\313c\355.p\265\321\370\345\261P@T\207)ro\240:\202\023likely benign Octal-escaped bytes within a large zlib-compressed binary literal in httptools' generated parser.c.Reasoning
Raw-pass octal escape run inside a long binary byte string. The adjacent embedded-NUL finding shows it is part of one zlib-style blob (starts with x\332). Compressed binary data embedded as a C literal in a generated parser file is a common, legitimate pattern. Nothing in the snippet decodes or executes it, and raw findings carry a higher false-positive rate.
-
6\321G\216=\372\270\307\374\004~B\337\331\315\2567\266\261\354\314\314\363\274_\363\314\314\233u\345\001\020\313c\355.p\265\321\370\345\261P@T\207)ro\240:\202\023likely benign Long run of octal-escaped bytes inside the httptools parser C source, consistent with embedded compressed binary data.Reasoning
The snippet is a long run of octal escapes whose bytes look like zlib-compressed binary data (the surrounding token finding shows a literal starting with 'x\332', the zlib header). Compressed binary embedded as a C string in a parser source file is typical of a test fixture or generated data, not an obfuscated payload. The file is part of the httptools library, and nothing here executes or decodes anything. Raw-pass octal findings have a high false-positive rate.
-
\355.p\265\321\370\345\261P@T\207)ro\240:\202\023likely benign Another segment of the same octal-escaped binary blob in parser.c.Reasoning
Same blob as the other findings on this line: high-entropy binary bytes written as octal escapes inside a C string literal. The entropy (2.6 bits/byte) and byte distribution fit compressed data, and the snippet shows no code, decoding logic or execution.
-
2\023likely benign Continuation of the embedded binary blob, written as octal escapes.Reasoning
Continuation of the same embedded compressed-data literal. The snippet contains only byte escapes with no executable logic, and the raw pass is prone to flagging such data.
-
info
warn→ info by reviewembedded-nul-in-stringhttptools/parser/parser.c:12096:559new in this releasestatic const char cstring = "x\332uUMo\023G\030&\010\265@\214\210q\224\200haLi\223\200\342\312j\332\244\037j\033\021h\221\nM\370\020\252\252j4\336}\327\336\262\236Y\357\314\232\030\204\3041G\037\367\270\307=\356\321G\216=\372\270\307\374\004~B\337\331\315\2567\266\261\354\314\314\363\274_\363\314\314\233u\345\001\020likely benign A static const char array holding zlib-like compressed bytes, including an embedded NUL.Reasoning
The token pass flags a string literal holding binary data that includes an embedded NUL, which is how a C string represents raw compressed bytes. The literal is a static const char array named 'cstring' with a zlib-style 'x\332' header, pointing to test or fixture data rather than a dropper. The token pass does not show any code that reads or runs this data, so the reading is benign but not fully settled.
-
023\262\3068\027\212)likely benign More octal-escaped binary bytes in the same compressed literal.Reasoning
Further octal-escaped binary bytes continuing the same compressed literal. No code or decoding appears in the snippet, and the context is a library source file.
-
12\3566o\257\021\323\3660\211\335\007\355\375\2009\022\032\177\272\332\2029\177\267\204p\376a\246I\321\013Llikely benign Continuation of the octal-escaped compressed blob in parser.c.Reasoning
Same embedded binary literal as the other findings in this file, with no executable or decoding code in the snippet. Entropy and escape density match compressed data.
-
\177\272\332\2029\177\267\204p\376a\246I\321\013Llikely benign Higher-entropy octal-escaped bytes within the same embedded data literal.Reasoning
Octal escapes with rising entropy (3.0 bits/byte), still consistent with compressed binary data stored in a C literal. The snippet shows no code that decodes or executes the bytes.
-
0\365\337\266\321Q\312U\310\313\206\313<\t^\003<Ox\262\200\277\316\340\223\241\341\016\016m\336g\216m\222\0160\023<\254\022+\001likely benign Dense run of octal escapes in the embedded binary literal.Reasoning
A run of 10 octal escapes at about 3.1 bits/byte. This is still compressed-looking binary embedded as a string literal, and nothing in the snippet decodes or runs it. Long byte runs like this are common in generated or test C source.
-
+\312Q\2420\024Z\3636x\302\227\324\001n\0037l\220e\223\216\360\035\223\276\004p)n\272\017\263\234\357\266=\024bB\334c\216\323b\306\313\373Z\310\t<\265|\230\251\370\010p\027\346|\356)\356\323\227\363\271\347O\376\230\"\236O\352x\002=\037\244\312\360\031`\276\300\323&su>m\244\245\355\246\365g\234t\005\227P\316ZF>\226v\31likely benign Tail portion of the same octal-escaped binary literal.Reasoning
Continuation of the embedded compressed-data literal. The snippet has no code and nothing that acts on the bytes, which fits a raw-pass false positive on binary test data.
-
324\001n\0037l\220e\223\216\360\035\223\276\004p)n\272\017\263\234\357\266=\024bB\334c\216\323b\306\313\373Z\310\t<\265|\230\251\370\010p\027\346|\356)\356\323\227\363\271\347O\376\230\"\236O\352x\002=\037\244\312\360\031`\276\300\323&su>m\244\245\355\246\365g\234t\005\227P\316ZF>\226v\312\346#yOY\351\3042\025\207\032\likely benign A long byte-string literal of binary octal escapes in the generated httptools parser.c.Reasoning
Raw-pass octal escapes inside a long byte-string constant in a generated C file. The run is one of many consecutive binary-looking escapes across the same region, consistent with an embedded binary constant (such as Cython-serialized data) rather than a payload. No decode or execution sink is visible in the snippet. Raw findings have a high false-positive rate.
-
13\373Z\310\t<\265|\230\251\370\010p\027\346|\356)\356\323\227\363\271\347O\376\230\"\236O\352x\002=\037\244\312\360\031`\276\300\323&su>m\244\245\355\246\365g\234t\005\227P\316ZF>\226v\312\346#yOY\351\3042\025\207\032\302\204\374\236S\272?8\304\337\036\276C\372\030\016\325\023\260(\036\033\0228dO\006\364\334\020\\!\25likely benign Continuation of the same binary octal-escape byte-string literal in parser.c.Reasoning
Same contiguous binary constant as the neighbouring findings. The entropy is moderate and the bytes look like serialized or compressed data in a generated source file. Nothing in the snippet decodes or runs it.
-
65g\234t\005\227P\316ZF>\226v\312\346#yOY\351\3042\025\207\032\302\204\374\236S\272?8\304\337\036\276C\372\030\016\325\023\260\375\214likely benign Another segment of the binary byte-string constant in the generated parser.c.Reasoning
Part of the same long binary constant in a generated parser source. Raw octal-run detection fires on any binary-literal blob, and no execution or network path is shown.
-
25\207\032\302\204\374\236S\272?8\304\337\036\276C\372\030\016\325\023\260\375\214\002\224*\024\035\007likely benign Another segment of the binary byte-string constant in parser.c.Reasoning
Same binary constant region. The snippet shows only escaped bytes with no code that consumes them as code.
-
0}\047E8\353\246#\336~zb\246\247}\245\257\274&z>sr\243\374\322\317\354\267\000\340P/\364\365\313}d)\375\214\002\224*\024\035\007likely benign Further binary octal-escape bytes in the generated parser.c constant.Reasoning
Binary octal-escape run within the same generated constant. Raw-pass entropy alone does not show malicious intent, and the snippet contains no decode, exec or spawn calls.
-
0\227U4\n@\266|\313ppB\261z\3451\003\364%\324\257A\377\364\365\306\227\215_\352\n\231\275q8,\036\214%\274.S\323oer\300S\212\3174\215l\260\025te\366\216\0245:>\177\211\341q\335V\235\034Mka\026\366Ij8XH\216\2374\223|9yp9\"\362C6<\332\002\254\027\250c\315!\035+\017\257\363\317\030Lh/\347\244\213Z\311\262\027\225\366\353""likely benign Binary octal-escape data continuing the generated constant in parser.c.Reasoning
Same embedded binary constant. The snippet is raw data with no visible consumer that executes it.
-
250c\315!\035+\017\257\363\317\030Lh/\347\244\213Z\311\262\027\225\366\353""\"1J\311\245\205\0246\007ab\257\315\211\023\221\360\204Z\302\034\340\220\371\032\242\353:\240\240\000\262\255\341rj\"\313\246]\220\222\265\001\267\326\266yi]2\311\364\307\211\3579\342\025\307J(\036y\246\274+\\\327\023J\030x&\340X\037\353l\210\2likely benign Continuation of the binary byte-string literal in the generated parser.c.Reasoning
Same binary constant region. Only escaped byte data is shown, with no decode-and-run pattern.
-
1\262\027\225\366\353""\"1J\311\245\205\0246\007ab\257\315\211\023\221\360\204Z\302\034\340\220\371\032\242\353:\240\240\000\262\255\341rj\"\313\246]\220\222\265\001\267\326\266yi]2\311\364\307\211\3579\342\025\307J(\036y\246\274+\\\327\023J\030x&\340X\037\353l\210\2374\347\231\306v\272\233e\377U\260\323\340s\177\267\2likely benign Another binary octal-escape run in the generated parser.c constant.Reasoning
Same embedded binary data. The octal-run signal is a byte-level pattern and the snippet has no executable sink.
-
11\245\205\0246\007ab\257\315\211\023\221\360\204Z\302\034\340\220\371\032\242\353:\240\240\000\262\255\341rj\"\313\246]\220\222\265\001\267\326\266yi]2\311\364\307\211\3579\342\025\307J(\036y\246\274+\\\327\023J\030x&\340X\037\353l\210\2374\347\231\306v\272\233e\377U\260\323\340s\177\267\220\234\273xtwx\360n79\177\371likely benign A further binary octal-escape segment of the generated constant.Reasoning
Same binary constant. Entropy near 3 bits per byte is typical of compressed or serialized data embedded in generated code, and no execution is shown.
-
info
warn→ info by reviewembedded-nul-in-stringhttptools/parser/parser.c:12096:2128new in this releaseh/\347\244\213Z\311\262\027\225\366\353""\"1J\311\245\205\0246\007ab\257\315\211\023\221\360\204Z\302\034\340\220\371\032\242\353:\240\240\000\262\255\341rj\"\313\246]\220\222\265\001\267\326\266yi]2\311\364\307\211\3579\342\025\307J(\036y\246\274+\\\327\023J\030x&\340X\037\353l\210\2374\347\231\306v\272\233e\377U\260\likely benign An embedded-NUL string literal carrying the same binary blob in the generated parser.c.Reasoning
A string literal with an embedded NUL that runs over a large binary blob. Generated C from a binary-data serializer commonly produces this, and it matches the surrounding constant. The token pass is less reliable here, and the snippet shows no sink that uses the bytes.
-
\032\242\353:\240\240\000\262\255\341rj\"\313\246]\220\222\265\001\267\326\266yi]2\311\364\307\211\3579\342\025\307J(\036y\246\274+\\\327\023J\030x&\340X\037\353l\210\2374\347\231\306v\272\233e\377U\260\323\340s\177\267\220\234\273xtwx\360n79\177\371H\rw\306\327\267\342\335\370\331\250\252\221\365\350\\tB4\207\017\202\likely benign Binary byte-string literal embedded in the generated httptools C parser.Reasoning
A run of octal-escaped bytes inside a generated C source file for httptools. Cython and Ragel-generated parsers embed constant byte-string tables like this, and the sequences are contiguous with the neighbouring findings. Nothing in the snippet shows execution or decoding logic, so this looks like a generated data literal rather than a dropper.
-
23\340s\177\267\220\234\273xtwx\360n79\177\371H\rw\306\327\267\342\335\370\331\250\252\221\365\350\\tB4\207\017\202\372)\254\237y\025\353W\303vp\020X\341\243x%\356\225\230\225\361\312FT\035\337\331likely benign Continuation of the binary byte-string literal in the generated httptools parser.Reasoning
Same long run of octal-escaped bytes from the same generated literal, continuing the sequence from the previous finding. It is a data table in generated code with no executable or network behaviour visible.
-
?\214p|\355NTOH3\256&\237mF\007\311\027\230/I\261likely benign Further segment of the binary constant data in the generated parser source.Reasoning
Contiguous octal-escaped bytes from the same generated C literal. The entropy is consistent with compiled or serialized constant data, and the snippet contains no decoding or execution calls.
-
Q5\251}\033\037L\260\033A;<Hj:K\201}\031\276\300likely benign Binary data segment in the generated httptools parser literal.Reasoning
Another segment of the same octal-escaped constant literal inside generated parser.c. It is low-entropy-looking data with no code path that would act on it.
-
326\243O\243^R\373q\324\234`\033\321j\274\220\324t\231\005\266\031\275\300\355\324~}_\312q7\332\2161\307\317\243,\307\273\335\017\027\317\\\272\031\260\017\237\234\271P\031/~\216\252\261\244re|\005eB\031*\253\303\303@bU\225k\301\315\010\343,\0171\301\352P\006\365d\251\212N\227j\303\372pk\330K*7\002\026\364\303\347Qjlikely benign Binary constant data segment within the generated parser source.Reasoning
Octal escapes forming part of the same embedded constant data block. Raw-pass octal-run signals are common false positives in generated C, and this shows no obfuscated logic.
-
031\275\300\355\324~}_\312q7\332\2161\307\317\243,\307\273\335\017\027\317\\\272\031\260\017\237\234\271P\031/~\216\252\261\244re|\005eB\031*\253\303\303@bU\225k\301\315\010\343,\0171\301\352P\006\365d\251\212N\227j\303\372pk\330K*7\002\026\364\303\347Qjlikely benign Generated binary literal fragment in httptools parser.c.Reasoning
Part of the same contiguous generated byte literal. The raw pass flagged only the escape pattern and entropy; the file context points to a generated data table.
-
q7\332\2161\307\317\243,\307\273\335\017\027\317\\\272\031\260\017\237\234\271P\031/~\216\252\261\244re|\005eB\031*\253\303\303@bU\225k\301\315\010\343,\0171\301\352P\006\365d\251\212N\227j\303\372pk\330K*7\002\026\364\303\347Qjlikely benign Binary data fragment from the generated httptools C parser.Reasoning
Same generated octal-escaped literal, with no surrounding decode, exec, or process-spawn behaviour in the snippet. The raw pass is known to over-flag such constant tables.
-
\035\257\254\205\275\350||6^\033\325F\273\307\350\217\242\220p!\304p\213Glikely benign Binary constant segment in the generated parser source.Reasoning
Octal escapes from the same long constant literal in the generated file. The pattern matches embedded binary tables, not an encoded payload pipeline.
-
221\031\337\321\305\327\307\365\357b\026\253Q\363C\345\314\325\255\270\031\357\215\026pZ]\035\257\254\205\275\350||6^\033\325F\273\307\350\217\242\220p!\304p\213Glikely benign Generated binary data within the httptools parser C file.Reasoning
Continuation of the same generated byte-string literal. The snippet is pure data with no execution path, and the finding is a raw-pass encoding heuristic.
-
6\253Q\363C\345\314\325\255\270\031\357\215\026pZ]\035\257\254\205\275\350||6^\033\325F\273\307\350\217\242\220p!\304p\213Glikely benign Trailing segment of the binary constant in the generated httptools parser.Reasoning
Final segment of the same octal-escaped literal in the generated parser. It ends the string constant with no code acting on the bytes shown.
-
57\215\026pZ]\035\257\254\205\275\350||6^\033\325F\273\307\350\217\242\220p!\304p\213Glikely benign Octal-escaped binary data literal inside generated Cython parser code.Reasoning
The octal escapes sit inside a large byte-array constant in a Cython-generated C file. Serialized code-object data routinely produces runs of high-byte escapes, and the snippet has no executable logic.
-
50\217\242\220p!\304p\213Glikely benign Continuation of the same octal-escaped binary constant in generated Cython code.Reasoning
Same byte-array blob in the generated parser.c. Raw-pass octal runs in a compiled-extension C file are expected serialized data, not obfuscated logic.
-
2^\244\333\210\226\243\277b\246S!\031\334\306\275-\325\260\334\267\251\252\313+C\021>\303\343Z\276\032\\\016q\013W\206\365\377\001\005\303\307\362";likely benign Further octal-escaped binary data in the generated Cython parser source.Reasoning
The snippet is the tail of the same generated byte-array constant. No decoding or execution appears, and the raw-pass entropy is typical of marshalled data.
-
67\251\252\313+C\021>\303\343Z\276\032\\\016q\013W\206\365\377\001\005\303\307\362";likely benign End of the octal-escaped binary blob in generated Cython code.Reasoning
The snippet is the end of the same generated binary blob, which terminates the literal. It is consistent with Cython's embedded marshalled-code output.
-
info
warn→ info by reviewembedded-nul-in-stringhttptools/parser/parser.c:12105:224new in this releasestatic const char cstring = "\377(tree fr\377agment).\377?Note th\377at Cytho\377n is del\377iberatel\377y strict\373er!\001n PEP\377-484 and\377 rejects\377 subclas\377ses of b\377uiltin t\377ypes. If\377 you nee?d to p%\000%\t\377then set\376\200\000e \047anno\177tation_<\000\377ing\047 dir\366b\000iv\242\000o Fa\2likely benign Long C string constant carrying Cython-embedded serialized code with NUL bytes.Reasoning
The string holds Cython's embedded marshalled code object: it includes Cython's own error-message text ('tree fragment', 'Cython is deliberately strict') mixed with binary bytes. NUL bytes inside such a constant are normal for this compiled-extension output and the literal is not executed by any suspicious path.
-
0021p]\000 \004\007\001vt\306\205\001Z\001\017qual\035\005\355\204\005\267\204\016\207\205\006\003ex\216\001\373aQ\005\315\204\006\250\000\321\204\016\347__t\313@\302\000is_\377coroutin\377easyncio\375.\010\006sbufcl\372\027\000_\273\000trace\360\201\204\001\212\205\001\216\205\001\333\204\001erre\277rr_pos\336\206\003likely benign Serialized Python bytecode fragment with octal escapes in generated parser source.Reasoning
Octal escapes in the generated embedded-code constant of the httptools Cython parser. The surrounding text mirrors Python code-object names (is_coroutine, asyncio, traceback), which is consistent with serialized bytecode, not hidden malicious logic.
-
04\005\267\204\016\207\205\006\003ex\216\001\373aQ\005\315\204\006\250\000\321\204\016\347__t\313@\302\000is_\377coroutin\377easyncio\375.\010\006sbufcl\372\027\000_\273\000trace\360\201\204\001\212\205\001\216\205\001\333\204\001erre\277rr_pos\336\206\003e\375x\250\205\006format\340\234\205\r\327G\343,\244\207\016\266likely benign Additional segment of the serialized bytecode constant in generated code.Reasoning
Same generated embedded-bytecode constant. The high-byte escapes interleave with identifier fragments typical of marshalled code objects, which Cython emits as-is.
-
yncio\375.\010\006sbufcl\372\027\000_\273\000trace\360\201\204\001\212\205\001\216\205\001\333\204\001erre\277rr_pos\336\206\003e\375x\250\205\006format\340\234\205\r\327G\343,\244\207\016\266\207\003ite\373ms\302\205\003t_chu\357nked\324\205\001gth\374\016\005\207\002after_\003cl\206\000&\005\306\207\0045\005\347\205\likely benign Generated binary constant containing parser callback names inside escaped bytes.Reasoning
Continuation of the generated marshalled-bytecode literal. Identifier fragments (on_message_complete, chunked, content-length) match the HTTP parser's callback names, which Cython serializes into its embedded code.
-
05\312\207\004o\377n_bodyon\374\354\003\237@mplete\034\010\006\242\211\003on_\000\006\263\211\004\037\t\177message\330\000\277ginon_\010\005c\371oE\006""\354\204\003on_ur\377lowning_\374\360@\260\212\003poppro\377tocolsel}f\302\210\025setde\230\212\002\341s\311\210\r\n\004\307\210\004\320\213\003val\377ues\200\001\330\likely benign Serialized symbol table fragment for the HTTP parser callbacks in generated code.Reasoning
Same generated data literal. The identifiers present (on_body, on_message_complete, upgrade, protocol) correspond to httptools callback names, indicating a compiled-in serialization of the parser's own symbols.
-
\374\354\003\237@mplete\034\010\006\242\211\003on_\000\006\263\211\004\037\t\177message\330\000\277ginon_\010\005c\371oE\006""\354\204\003on_ur\377lowning_\374\360@\260\212\003poppro\377tocolsel}f\302\210\025setde\230\212\002\341s\311\210\r\n\004\307\210\004\320\213\003val\377ues\200\001\330\004\n\377\210+\220Q\200A\33likely benign Generated binary fragment with parser identifiers in the compiled C source.Reasoning
Generated embedded-data fragment from the Cython parser. It contains the parser's own identifiers mixed with binary bytes, consistent with marshalled code objects and not with a dropper.
-
el}f\302\210\025setde\230\212\002\341s\311\210\r\n\004\307\210\004\320\213\003val\377ues\200\001\330\004\n\377\210+\220Q\200A\330\010\377\017\210t\2208\320\0334\277\260A\260T\270\021\016\001\250\177\0likely benign Remaining serialized data in the generated httptools parser constant.Reasoning
Last visible part of the same generated constant. Nothing in the snippet decodes or runs data; it is plain serialized data in a vendored extension's generated C file.
-
info
warn→ info by reviewembedded-nul-in-stringhttptools/parser/parser.c:12105:2434new in this releasege\330\000\277ginon_\010\005c\371oE\006""\354\204\003on_ur\377lowning_\374\360@\260\212\003poppro\377tocolsel}f\302\210\025setde\230\212\002\341s\311\210\r\n\004\307\210\004\320\213\003val\377ues\200\001\330\004\n\377\210+\220Q\200A\330\010\377\017\210t\2208\320\0334\277\260A\260T\270\021\016\001likely benign A generated C string literal in httptools' parser holding binary table data with embedded NUL bytes.Reasoning
The literal is a long binary blob in a generated C parser file. Embedded NULs and octal escapes in a single long string are typical of serialized state tables emitted by a code generator such as Cython or llhttp, not of hidden code. The token signal reflects the byte layout, not malicious string construction.
-
60q\330\0478\377\270\001\330+<\270A\330\277):\270!\340\010\201\004\013\377\320\013\033\2307\240!\330\377\023.\250a\330\020\030\230\367\001\330\010\021\000\"\240\047\250\277\021\330\0235\260Q\n\007\036?\230g\240Q\330\023b\001\037\006\027%\240W\313\000\023X\0013\006<\021\177$\240G\2501\330\023\205\001\376[\006(\250\007\2likely benign A run of octal escapes inside the same generated binary data literal in httptools' parser.c.Reasoning
The run of octal escapes is part of the same binary table literal in a generated parser source file. Its entropy and escape density match serialized binary data. The raw-pass signal has a high false-positive rate, and nothing in the snippet executes or decodes anything at runtime.
-
04\013\377\320\013\033\2307\240!\330\377\023.\250a\330\020\030\230\367\001\330\010\021\000\"\240\047\250\277\021\330\0235\260Q\n\007\036?\230g\240Q\330\023b\001\037\006\027%\240W\313\000\023X\0013\006<\021\177$\240G\2501\330\023\205\001\376[\006(\250\007\250q\330\023\367;\2701n\007)\250\027\260\347\001\330\023\243\001\likely benign Another segment of the generated binary table in httptools' parser.c, flagged for octal escapes.Reasoning
This is a continuation of the same generated binary table literal. The escape pattern is consistent with compiled state-machine data in a well-known HTTP parsing library, so the raw encoding flag is a false positive for this context.
-
23.\250a\330\020\030\230\367\001\330\010\021\000\"\240\047\250\277\021\330\0235\260Q\n\007\036?\230g\240Q\330\023b\001\037\006\027%\240W\313\000\023X\0013\006<\021\177$\240G\2501\330\023\205\001\376[\006(\250\007\250q\330\023\367;\2701n\007)\250\027\260\347\001\330\023\243\001\203\006-\250W\177\260A\330\023@\300\001\22likely benign A further octal-escaped segment of the same generated binary literal in httptools' parser.c.Reasoning
The snippet continues the same generated binary blob. Octal escapes at this density are the expected form of a serialized table in C source, and the context is a mainstream HTTP parser package.
-
001\376likely benign Octal-escaped binary data inside httptools' generated parser.c literal.Reasoning
Same generated binary data literal. The escape density and entropy are consistent with packed parser tables. The raw-pass finding alone does not indicate obfuscated code, and the surrounding file is a generated parser.
-
03\377\200A\360\n\000\r\037\230\377a\360\006\000\t\014\320\013\375\035\263 a\330\014\022\320\022\374\244 \230 \014\027\220x\230s\276\343\000\014\031\230\037\250E\000\024\377\220A\330\020\027\220s\230\357!\330\020\0212\000\r\023\220\377!\2204\220q\330\014\036\277\230a\230v\240U1\001\031\327\230\021\3302\005\340%\022\340likely benign Octal-escaped binary table data in the generated httptools parser source.Reasoning
The snippet is part of the generated binary table literal with no executable constructs. Octal escapes of this kind are how C generators encode binary tables, so the flag is a false positive.
-
7\230\377a\360\006\000\t\014\320\013\375\035\263 a\330\014\022\320\022\374\244 \230 \014\027\220x\230s\276\343\000\014\031\230\037\250E\000\024\377\220A\330\020\027\220s\230\357!\330\020\0212\000\r\023\220\377!\2204\220q\330\014\036\277\230a\230v\240U1\001\031\327\230\021\3302\005\340%\022\340\010\367\t\330\014\340A9\2likely benign Another octal-escaped data segment in httptools' generated parser.c.Reasoning
Same generated binary blob in a parser source file. The snippet holds only data bytes and no calls, decoding logic or network activity, consistent with a benign generated table.
-
30\014\022\320\022\374\244 \230 \014\027\220x\230s\276\343\000\014\031\230\037\250E\000\024\377\220A\330\020\027\220s\230\357!\330\020\0212\000\r\023\220\377!\2204\220q\330\014\036\277\230a\230v\240U1\001\031\327\230\021\3302\005\340%\022\340\010\367\t\330\014\340A9\230I\240\377S\250\002\250$\250d\260\375*\341 \020!\32likely benign Octal-escaped segment of the generated binary literal in httptools' parser.c.Reasoning
This is a continuation of the same generated binary table literal. Nothing in the snippet suggests dynamic execution or a payload, and the pattern fits packed parser state data.
-
220\377!\2204\220q\330\014\036\277\230a\230v\240U1\001\031\327\230\021\3302\005\340%\022\340\010\367\t\330\014\340A9\230I\240\377S\250\002\250$\250d\260\375*\341 \020!\320!6\260\377a\260t\2701\360\014\000\377\0304\2601\260D\270\001\376\010\000\021\027\320\026\047\240q\377\250\010\260\002\260\047\270\023\367\270A\340=\0likely benign A further segment of generated binary data in httptools' parser.c flagged by the raw pass.Reasoning
The escape run is part of the generated binary table in the parser source. The data is consistent with serialized parser tables and carries no executable semantics, so the raw signal is a false positive here.
-
\260\377a\260t\2701\360\014\000\377\0304\2601\260D\270\001\376\010\000\021\027\320\026\047\240q\377\250\010\260\002\260\047\270\023\367\270A\340=\000q\330\020 \377\240\001\240\021\340\010\013\210\3674\210zs\001\021\320\021\250\024\250Y\260\316\000]\017\031\001\230$\230\247@\023\254\000\375}\321\"\024\026\220likely benign Octal-escaped binary data in the generated httptools parser.c literal.Reasoning
Same generated binary data literal. The density of octal escapes and the entropy match packed tables in a generated C file from a known HTTP parsing library, and the snippet contains no code that runs.
-
\260D\270\001\376\010\000\021\027\320\026\047\240q\377\250\010\260\002\260\047\270\023\367\270A\340=\000q\330\020 \377\240\001\240\021\340\010\013\210\3674\210zs\001\021\320\021\250\024\250Y\260\316\000]\017\031\001\230$\230\247@\023\254\000\375}\321\"\024\026\220o\240T\276\254@\024\030\230\017\240\300\000\0likely benign Generated httptools parser state-table data written as octal escapes.Reasoning
The run of octal escapes is a byte-string state table in the generated httptools parser (the file is part of the httptools C extension, which uses generated state machines). Entropy around 3 bits per byte and the repeated structure fit compiled lookup tables, not a payload. The raw pass is known to over-flag such data.
-
60\002\260\047\270\023\367\270A\340=\000q\330\020 \377\240\001\240\021\340\010\013\210\3674\210zs\001\021\320\021\250\024\250Y\260\316\000]\017\031\001\230$\230\247@\023\254\000\375}\321\"\024\026\220o\240T\276\254@\024\030\230\017\240\300\000\022\003\220!";likely benign Continuation of the generated httptools parser table literal.Reasoning
Same generated parser table in httptools/parser/parser.c, ending in a closing string literal typical of generated C tables. No execution, decoding, or network behavior is present in the snippet.
-
\023\254\000\375}\321\"\024\026\220o\240T\276\254@\024\030\230\017\240\300\000\022\003\220!";likely benign Tail of a generated httptools parser data table.Reasoning
Tail of the same generated byte table in the httptools C parser; the snippet shows only data bytes and a string terminator, consistent with a Ragel/llhttp-style state machine.
-
70\001\330+<\270A\330):\270!\340\010likely benign Generated transition-table bytes in the httptools parser source.Reasoning
Repeated patterns of octal escapes with a limited byte alphabet are typical of generated transition tables in the httptools parser C source. Nothing in the snippet decodes or runs data, and the file context is a well-known HTTP parser library.
-
0A\330\010\013\320\013\033\2307\240!\330\023.\250a\330\020\030\230\001\330\010\013\320\013\"\240\047\250\021\330\0235\260Q\330\020\030\230\001\330\010\013\320\013\036\230g\240Q\330\0231\260\021\330\020\030\230\001\330\010\013\320\013%\240W\250A\330\0238\270\001\330\020\030\230\001\330\010\013\320\013\033\2307\240!\330\likely benign Generated parser table data within httptools C source.Reasoning
Generated parser table data in httptools/parser/parser.c. The repetitive structure of the escapes matches compiled state-machine tables, with no code-execution construct visible.
-
23.\250a\330\020\030\230\001\330\010\013\320\013\"\240\047\250\021\330\0235\260Q\330\020\030\230\001\330\010\013\320\013\036\230g\240Q\330\0231\260\021\330\020\030\230\001\330\010\013\320\013%\240W\250A\330\0238\270\001\330\020\030\230\001\330\010\013\320\013\033\2307\240!\330\023.\250a\330\020\030\230\001\330\010\013\likely benign Generated parser table bytes, benign octal-escaped constants.Reasoning
Same generated table pattern in the httptools parser. The high density of octal escapes reflects compiler-style serialization of constant tables, not hidden logic.
-
30\010\013\320\013\"\240\047\250\021\330\0235\260Q\330\020\030\230\001\330\010\013\320\013\036\230g\240Q\330\0231\260\021\330\020\030\230\001\330\010\013\320\013%\240W\250A\330\0238\270\001\330\020\030\230\001\330\010\013\320\013\033\2307\240!\330\023.\250a\330\020\030\230\001\330\010\013\320\013$\240G\2501\330\0237\26likely benign Generated parser constants flagged by octal-escape density.Reasoning
Repeated state-table constants in a generated C parser. The raw-pass encoding-octal signal fires on the escape density alone, and the context shows an ordinary parser library.
-
230\001\330\010\013\320\013\036\230g\240Q\330\0231\260\021\330\020\030\230\001\330\010\013\320\013%\240W\250A\330\0238\270\001\330\020\030\230\001\330\010\013\320\013\033\2307\240!\330\023.\250a\330\020\030\230\001\330\010\013\320\013$\240G\2501\330\0237\260q\330\020\030\230\001\330\010\013\320\013likely benign Generated parser table data, no executable behavior shown.Reasoning
Generated table in the httptools parser C file. No dynamic evaluation, process spawning, or network use appears; the bytes are consistent with a Ragel-generated machine.
-
30\230\001\330\010\013\320\013%\240W\250A\330\0238\270\001\330\020\030\230\001\330\010\013\320\013\033\2307\240!\330\023.\250a\330\020\030\230\001\330\010\013\320\013$\240G\2501\330\0237\260q\330\020\030\230\001\330\010\013\320\013\250\027\260\001\330likely benign Generated state-machine constants in httptools parser.Reasoning
Repetitive octal-escaped byte constants typical of a generated HTTP parser state machine. The raw pass flags the escape run; the surrounding code context is a standard library extension.
-
01\330\010\013\320\013\033\2307\240!\330\023.\250a\330\020\030\230\001\330\010\013\320\013$\240G\2501\330\0237\260q\330\020\030\230\001\330\010\013\320\013\250\027\260\001\330\023<\270A\330\020\030\230\001\330\010\013\320\013-\250W\260A\330\023@\300\0likely benign Generated parser table data, flagged only for octal-escape density.Reasoning
Generated parser table bytes within the httptools C extension. The pattern is compiler-style data, and the snippet shows no decoding or execution sink.
-
0\001\330\010\013\320\013$\240G\2501\330\0237\260q\330\020\030\230\001\330\010\013\320\013\250\027\260\001\330\023<\270A\330\020\030\230\001\330\010\013\320\013-\250W\260A\330\023@\300\001\330\020\030\230\001\330\010\013\320\013+\2507\260!\330\023>\27likely benign Generated parser table constants in the httptools C source.Reasoning
Same generated table series in httptools/parser/parser.c. The escapes are data constants from a parser generator and carry no sign of malicious intent.
-
01\330\010\013\320\013\250\027\260\001\330\023<\270A\330\020\030\230\001\330\010\013\320\013-\250W\260A\330\023@\300\001\330\020\030\230\001\330\010\013\320\013+\2507\260!\330\023>\270a\330\020\030\230\001\200A\360\n\000\r\037\230a\360\006\000\t\014\3likely benign A long octal-escaped byte-string literal inside Cython-generated httptools parser C code.Reasoning
The file is httptools' parser.c, which is Cython-generated C. Long runs of octal escapes with moderate entropy look like marshalled or pickled constant data embedded as string literals, a normal Cython output. Nothing in the snippet decodes or executes the bytes, and the raw pass has a high false-positive rate.
-
023;\2701\330\020\030\230\001\330\010\013\320\013)\250\027\260\001\330\023<\270A\330\020\030\230\001\330\010\013\320\013-\250W\260A\330\023@\300\001\330\020\030\230\001\330\010\013\320\013+\2507\260!\330\023>\270a\330\020\030\230\001\200A\360\n\000\r\037\230a\360\006\000\t\014\320\013\035\230Q\230a\330\014\022\320\022)likely benign Another octal-escaped constant blob in the generated httptools parser source.Reasoning
This is another run of octal escapes in the same generated constant data of httptools' Cython-generated parser.c. The snippet shows no decoding, execution or network use, so it fits serialized constants rather than a dropper.
-
330\010\013\320\013)\250\027\260\001\330\023<\270A\330\020\030\230\001\330\010\013\320\013-\250W\260A\330\023@\300\001\330\020\030\230\001\330\010\013\320\013+\2507\260!\330\023>\270a\330\020\030\230\001\200A\360\n\000\r\037\230a\360\006\000\t\014\320\013\035\230Q\230a\330\014\022\320\022)\250\021\250!\330\014\027\220xlikely benign Continuation of the generated octal byte-string in httptools' parser.c.Reasoning
The snippet continues the same generated byte-string constant in httptools' Cython output. The raw-pass octal finding alone does not show malicious behaviour, and the file context points to generated data.
-
30\230\001\330\010\013\320\013-\250W\260A\330\023@\300\001\330\020\030\230\001\330\010\013\320\013+\2507\260!\330\023>\270a\330\020\030\230\001\200A\360\n\000\r\037\230a\360\006\000\t\014\320\013\035\230Q\230a\330\014\022\320\022)\250\021\250!\330\014\027\220x\230s\240!\330\014\031\230\037\250\001\330\020\024\220A\330\likely benign A longer octal-escaped run within the generated httptools parser constants.Reasoning
A 12-escape octal run in the same generated Cython constant data. The entropy is consistent with marshalled bytecode or pickled objects. Nothing in the snippet runs or fetches anything.
-
0\001\330\010\013\320\013+\2507\260!\330\023>\270a\330\020\030\230\001\200A\360\n\000\r\037\230a\360\006\000\t\014\320\013\035\230Q\230a\330\014\022\320\022)\250\021\250!\330\014\027\220x\230s\240!\330\014\031\230\037\250\001\330\020\024\220A\330\020\027\220s\230!\330\020\021\360\006\000\r\023\220!\2204\220q\330\014\03likely benign Octal-escaped constant data within the generated httptools parser source.Reasoning
The snippet is again a run of octal escapes in the generated constant table of a Cython-built parser. No execution or network sink appears, and the file context accounts for the pattern.
-
info
warn→ info by reviewembedded-nul-in-stringhttptools/parser/parser.c:12114:3031new in this release010likely benign A long string literal with an embedded NUL, probably serialized binary constant data from the generated parser.Reasoning
Cython emits large binary constants as C string literals, and these can contain embedded NULs when the data is marshalled bytes. The token pass flags the NUL with no sign of concatenated sensitive names or macro tricks. The file is a known generated parser, so the NUL is most likely part of serialized data.
-
2\320\022)\250\021\250!\330\014\027\220x\230s\240!\330\014\031\230\037\250\001\330\020\024\220A\330\020\027\220s\230!\330\020\021\360\006\000\r\023\220!\2204\220q\330\014\036\230a\230v\240U\250!\330\014\031\230\021\330\014\027\220x\230s\240!\340\014\031\230\037\250\001\330\020\024\220A\330\020\027\220s\230!\330\020\021likely benign Octal-escaped constant data in the generated httptools parser C file.Reasoning
The snippet is an 11-escape octal run in the same generated httptools parser constants. It shows no decoding or execution, and the entropy and layout match serialized data.
-
037\250\001\330\020\024\220A\330\020\027\220s\230!\330\020\021\360\006\000\r\023\220!\2204\220q\330\014\036\230a\230v\240U\250!\330\014\031\230\021\330\014\027\220x\230s\240!\340\014\031\230\037\250\001\330\020\024\220A\330\020\027\220s\230!\330\020\021\340\010\t\330\014\017\210t\2209\230I\240S\250\002\250$\250d\260*\2likely benign Another generated octal-escape run in httptools' parser.c.Reasoning
Another run of octal escapes in the generated constant data of the Cython parser. There is no execution, network, or decoding logic in the snippet.
-
023\220!\2204\220q\330\014\036\230a\230v\240U\250!\330\014\031\230\021\330\014\027\220x\230s\240!\340\014\031\230\037\250\001\330\020\024\220A\330\020\027\220s\230!\330\020\021\340\010\t\330\014\017\210t\2209\230I\240S\250\002\250$\250d\260*\270A\330\020!\320!6\260a\260t\2701\360\014\000\0304\2601\260D\270\001\360\014\likely benign Octal-escaped constant data in httptools' generated parser source.Reasoning
The nine-escape octal run sits inside the generated constant table of httptools' Cython output. The surrounding bytes are data, not code that the snippet invokes.
-
50!\330\014\031\230\021\330\014\027\220x\230s\240!\340\014\031\230\037\250\001\330\020\024\220A\330\020\027\220s\230!\330\020\021\340\010\t\330\014\017\210t\2209\230I\240S\250\002\250$\250d\260*\270A\330\020!\320!6\260a\260t\2701\360\014\000\0304\2601\260D\270\001\360\014\000\021\027\320\026\047\240q\250\010\260\002\26likely benign A further octal-escaped segment of the generated constant data in httptools' parser.c.Reasoning
This is a continuation of the same generated binary constant in httptools' Cython-built parser.c. The raw pass alone is weak evidence, and no executable sink appears in the snippet.
-
0!\320!6\260a\260t\2701\360\014\000\0304\2601\260D\270\001\360\014\000\021\027\320\026\047\240q\250\010\260\002\260\047\270\023\270A\340\014\017\210q\330\020 \240\001\240\021\340\010\013\2104\210z\230\021\330\014\021\320\021\250\024\250Y\260a\330\014\017\210z\230\021\230$\230a\330\020likely benign Octal-escaped byte table inside the generated HTTP parser C source.Reasoning
Long runs of octal escapes in parser.c are the byte tables that Ragel-generated HTTP parsers emit for state machines. Raw-pass octal runs are a high false-positive pattern, and nothing in the snippet decodes or executes data.
-
\260D\270\001\360\014\000\021\027\320\026\047\240q\250\010\260\002\260\047\270\023\270A\340\014\017\210q\330\020 \240\001\240\021\340\010\013\2104\210z\230\021\330\014\021\320\021\250\024\250Y\260a\330\014\017\210z\230\021\230$\230a\330\020\023\2204\220}\240G\2501\330\024\026\220o\240likely benign Another segment of the generated parser state table.Reasoning
This is a continuation of the same generated Ragel-style state table in parser.c. It is a data table with no runtime decode or execution path visible.
-
002\260\047\270\023\270A\340\014\017\210q\330\020 \240\001\240\021\340\010\013\2104\210z\230\021\330\014\021\320\021\250\024\250Y\260a\330\014\017\210z\230\021\230$\230a\330\020\023\2204\220}\240G\2501\330\024\026\220o\240T\250\021\330\024\030\230\017\240q\330\014\022\220!";likely benign Continuation of the generated parser table ending in a C string literal.Reasoning
Same generated table pattern, ending in a normal C string terminator. The raw octal-run signal fires on ordinary generated data.
-
340\010\013\2104\210z\230\021\330\014\021\320\021\250\024\250Y\260a\330\014\017\210z\230\021\230$\230a\330\020\023\2204\220}\240G\2501\330\024\026\220o\240T\250\021\330\024\030\230\017\240q\330\014\022\220!";likely benign Generated parser table segment with octal byte escapes.Reasoning
Octal escapes within the generated parser table, with no decode or execution logic in the snippet.
-
\020\023\2204\220}\240G\2501\330\024\026\220o\240T\250\021\330\024\030\230\017\240q\330\014\022\220!";likely benign Final tail of the generated parser table literal.Reasoning
Tail of the generated parser table. The raw-pass octal signal is a known false-positive pattern for binary-looking generated data.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:546new in this release45@L#\227r\326\246\212\030\312C\244\215b\216\241*s\022\350\344\351\311\255\203\373\007\210\010\027)\372\033u\214F:h;\234hM5\222\036j\007\214\033&\220\tlikely benign Binary-looking octal-escaped byte data in the URL parser source.Reasoning
Octal escapes in url_parser.c that appear to be binary data, likely test fixture bytes. The snippet shows no decode or execution, so the raw signal is most likely a false positive.
-
info
warn→ info by reviewembedded-nul-in-stringhttptools/parser/url_parser.c:6357:691new in this releasestatic const char cstring = "x\332\255S\315\216\3336\020\216\221\r\340&\333\326\336\355f\035\364B\243i\323\"\033\007\233,6\311\246Ma\344\007\335\244\r\326)\272\010\322\003AK\224\315\226\"m\2222,\244\001r\364QG\035y\324\321G\037\375\010{\324\321\217\220G\350H\266l\027\333\366\322\n\22283\234o8\374f\346k\243(E\236\"\03likely benign Large zlib-compressed binary blob stored as a C string constant.Reasoning
The literal begins with a zlib header (x\332) and holds a large compressed blob. This is consistent with an embedded test fixture in a parser test suite. The snippet shows no code that decompresses or runs it, though the context is cut off.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:772new in this release\204\220\206\030&\005\0068\023\235\033\310e\n\016a\003\232\241\237\021\256i\203\270.\006?\3522M\332\234R\221\375;N\327\230\236\221\222\353F\217likely benign Further octal-escaped bytes of the compressed blob.Reasoning
Continuation of the compressed binary blob in the C string constant. Raw octal runs over compressed data are expected here and show no execution.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:836new in this release37\021\256i\203\270.\006?\3522M\332\234R\221\375;N\327\230\236\221\222\353F\217likely benign More octal-escaped bytes from the embedded compressed constant.Reasoning
Compressed data bytes in the same embedded constant. No decode or execution appears in the snippet.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:887new in this release327\230\236\221\222\353F\217likely benign High-entropy octal bytes in the embedded compressed constant.Reasoning
High-entropy compressed bytes in the embedded constant. This pattern is consistent with a test fixture and does not by itself indicate malicious intent.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:945new in this release\267\003\305\361\302\243\027\016\231\030\020\316\\\004\326\234\021\246\347\361\\!\201\007\217\004\334 \214\025u\003\207b\214\334 ODHq\013x\0310\302a\327a\202\031\214\263\020\300\036\034\206\270\024\235\243<&\247\242c\272\0311o\337\241vh\340\316t\350\000\033\371\335\221O\206\314\017\374\365\375\037 \341\223<\277\343yn\3likely benign Continuation of the compressed binary constant.Reasoning
Compressed binary data continues in the string constant. Nothing in the snippet runs or decodes it.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:1660new in this release03A\303\220\264Q\304\241m\342\374>/\277\047\225OL1\005\331\370\234\353\223UC0C}\315\205\364\274\\\317*\232\013n6^=\331\313&\256\027b83\2371E5\274\320!\363\031\325\224\330\274\360Q-\352\247\345\235\250\225\226\257Fd]\272\026W\027\277Z\\\372P\276p\351\223Q+\255]\267M\likely benign Octal-escaped marshal data inside generated Cython C source.Reasoning
The file is a Cython-generated C module (httptools url_parser). Cython embeds marshalled Python code-object data as long octal-escaped byte strings. The high-entropy octal run is that marshal blob, not a payload, and the snippet contains no decode or execution logic.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:1844new in this release6\2305\250b@\365\373R\272qyt3j\275/}\330\274\360Q-\352\247\345\235\250\225\226\257Fd]\272\026W\027\277Z\\\372P\276p\351\223Q+\255]\267M\333J\257likely benign Continuation of the marshalled constant blob in generated Cython code.Reasoning
Same file and pattern as the other octal findings: a continuation of Cython's embedded marshalled constant data. Raw byte-level matches in generated code have a high false-positive rate, and nothing here executes or decodes anything.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:1995new in this release325\331\0068FA\334\214_\203m\343RZ\2762:\214v\242v\356\377\361\366\331\326\315d?\255T""\323/\367\222fr:>\234Tg\345\355\350^\374\225-\301Ig;\260\235<\037likely benign Octal-escaped marshal data in generated Cython source.Reasoning
Octal-escaped binary data in a Cython-generated source file, consistent with marshalled code objects. No executable or network behavior is visible in the snippet.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:2130new in this release1Ig;\260\235<\037likely benign Binary constant data from the Cython-generated parser.Reasoning
The run is part of the same embedded marshal blob in the generated Cython module. The entropy is typical of compressed or marshalled bytecode, and the surrounding code is standard generated parser code.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6357:2574new in this release\017\354ir8\336\235\\\236\002\255likely benign Tail of the embedded marshal data in generated Cython C.Reasoning
Short octal run ending the same embedded constant string in generated Cython code. It is data, not code, and nothing in the snippet decodes or runs it.
-
info
warn→ info by reviewembedded-nul-in-stringhttptools/parser/url_parser.c:6366:339new in this releasestatic const char cstring = "\377(tree fr\377agment).\377<URL sch\377ema: {!r\177}, host\004\005wpor\002\007ath\034\005\037query)\005F\0059\005\377userinfo\376K\003>?Note \377that Cyt\377hon is d\377eliberat\377ely stri\357cter!\001n P\377EP-484 a\377nd rejec\377ts subcl\377asses of\377 builtin\377 types. \377If youlikely benign Cython-generated string constant holding marshalled data with embedded NULs and docstring text.Reasoning
The literal begins with the readable text of CPython error and documentation strings ('tree fragment', 'URL schema', 'Note that CPython is deliberately stricter'), with binary bytes in between. This is the usual form of Cython's marshalled code-object constants, which embed NULs and binary data. The file is a generated parser module, so it is not a sign of an attack.
-
info
warn→ info by reviewencoding-octalhttptools/parser/url_parser.c:6366:1195new in this releasedatacli\367ne_\262\000trac\337eback\371Cfo\017rmat\314\205\005\273\205\001\227n\207g\377itemslno\343ff\276b\316A\307bdpa\337thpop\356\205\001py9_q\000\337\205\002res\000\000\237`\376\236\206\003selfset\303de\261b\344`\344\205\005\337`ue\377s\200\001\330\004\n\210+\377\220Q\200\001\360\014\000\t\377\030\220q\330\010\025likely benign Marshalled identifiers and bytes in a generated Cython constant string.Reasoning
Octal escapes interleaved with readable identifiers ('traceback', 'format', 'itemsl', 'selfset') in a generated Cython constant. These are marshalled code-object names and bytes, typical of Cython output, not an obfuscated payload.
-
PyObject ** const __pyx_pyargnames = -
__pyx_r = -
static PyObject * -
PyObject* const varnames = -
,.type= HTTP_REQUEST ,.raw= "GET /δ¶/δt/pope?q=1#narf HTTP/1.1\r\n" "Host: github.com\r\n" "\r\n" -
,.fragment= "narf" ,.request_path= "/δ¶/δt/pope" ,.request_url= "/δ¶/δt/pope?q=1#narf" ,.num_headers= 1 -
,.request_path= "/δ¶/δt/pope" ,.request_url= "/δ¶/δt/pope?q=1#narf" ,.num_headers= 1 ,.headers=
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.
|
&&