Repository navigation
fix: fold a control-flow object that hides the decoder under --unsafe when its escapes all sit in branches - #464
Merged
Merged
Conversation
…tes all sit in branches, and rerun without it unless those uses are gone at the end
…nch and one that escapes in a live branch
…coder, so other programs are not run twice
… a decoder to any member call
…low object speculation on top of main
…es on top of main
This was referenced Nov 20, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OX2-D3:
--unsafedecoding when the decoder is hidden behind a control-flow object.In multi-layer obfuscator.io output, the string decoder is often passed to the control-flow object's call proxies (
f.qPqCs(decoder, "0x37")). The object could not be folded: dead-code injection had copied in a branch where it escapes (h[...](e, f)), and only the decoded strings show that branch is dead. Those strings could not be decoded while the decoder was still used as a value. So each blocked the other.Change (unsafe lane only, inside the existing escape speculation):
Rows:
cfo-escape-in-branch(pw011-n2--functions) decodes fully and prints the source's output.cfo-live-escapehas a live escape: the object is kept and the program prints what node prints.Full sweep, main @d50bd48c vs this branch (3,465 cases, 2,189 run):
Gained under unsafe: pw011-n2--functions, pw011-n2--control, pw011-n3--strings, pw024-m3--empty-log, pw024-m3--greeting, pw024-m3--functions, rnd001-m3--functions, rnd001-m3--objects, rnd001-m3--strings, rnd001-m3--console-test.
Gates:
--unsafeand doubled their time.untwist-ci --webgreen before the rebase over fix: refuse the object alias fold on Annex B block functions and lexical aliases read by hoisted functions #458/fix: nested-object fold respects a function's own name and enclosing with/eval #460/fix: judge shared inputs across every input (r5-ml6 F1-F5) #462. After the rebase, untwist and untwist-deobfuscate tests pass. The wasm baseline goes to 14,907,000 (cap 16,397,700) for 16,397,393 bytes.Still open (unsafe): rnd031-n3--strings and the rnd031-n2/n3 group. An outer unit's rotator that has already been decoded but is still kept now comes before the inner rotator, so the inner unit hits "code precedes the rotator". The stateful-decoder group (pw022-m3 x4: the string-array states class in statement form behind a compactness guard; pw011-m3, pw023-m3, rnd031-m2/m3--control). pw011-n3 and pw024-m3 classes/control/strings: decoders used as values inside other decoders' dead-injected bodies, or uses that only a later stage removes. pw023-m3/rnd031-m3: code before the rotator.