Recent searches
Search options
Administered by:
WHAT—
... "They point to how security researchers hated Visual Basic 6 binaries due to the complexity of reverse engineering the software, the presence of a Lua obfuscation layer in the 2012 Flame malware, and the Grip virus, which contained a Brainfuck interpreter coded in Assembly to generate its keycodes, as examples."
It can only be a matter of time until malware authors stumble across CLC-INTERCAL. And then we'll ALL be sorry!
https://www.theregister.com/2025/03/29/malware_obscure_languages/?td=rt-3a
@cstross Seems eminently sensible to me.
If I were inclined to write malware (which I am not) I'd use Brainfuck too. Maybe not code the interpreter in assembler though, I mean, there's INTERCAL for these things.
@Uilebheist How about a dialect of Brainfuck in which the various symbols it uses for commands are replaced with unicode glyphs in a homograph attack (glyphs that display identically but are actually separate characters, eg. the latin, cyrillic, and greek letter "o" are all different in unicode)? Preferably whitespace homoglyphs or combinations: for example, you could encode all 8 Brainfuck instructions using three-character combos of space and zero-width space.
@cstross @Uilebheist
Before COVID, I used to play Gõ with one of the people who invented the "Whitespace" language. It seemed obviously an extension from the black&white simplicity of the game.