#OpCodes
threw the opps into the arbitrary code execution, turned his ass into some MIPS opcodes
An account with this avatar was just blocked.
November 9, 2026 at 4:09 AM
so now when you're designing your new BASIC you can just think about the assembly code and not have to hand-assemble it into opcodes

and then you might decide to modify the assembler to disassemble, letting you view and edit existing code
November 8, 2026 at 8:34 PM
🍻 csound-plugins 🍻

Additional opcodes for Csound

🔗 https://github.com/csound/plugins

#homebrew #newpkg #macos #linux #formula
November 8, 2026 at 6:01 PM
If you were a bedroom coder in 1983, your entire software development toolkit consisted of a ZX Spectrum, a cassette deck, and a magazine with a list of Z80 opcodes in the back. Most of those games worked. The ones that didn't, you debugged by staring at the screen until your eyes hurt.
November 3, 2026 at 2:00 PM
Actually ok no, the only idiosyncrasy vs my preferences is that they use store to describe loading an immediate into a register

fwiw the GB opcodes call everything load, so unless you want to do that you kind of have to name them however you prefer
November 9, 2026 at 1:07 AM
yes they have a vaguely similar structure but yoyo uses a completely different and incompatible set of opcodes so Why would you call it a qoi
November 2, 2026 at 6:56 PM
would be useful to know if this needs new opcodes or works within current script. HTLCs already have tight timing constraints, curious how PQ sigs affect that math.
November 2, 2026 at 8:45 PM
Fed Aether a scrambled JavaScript heap to automate the deobfuscation of a custom VM. Now I have readable opcodes and a clear control flow graph.

Who else is reverse-engineering packed JS this week? #malwareanalysis #RE
November 2, 2026 at 5:00 PM
Build the emulator anyway and keep the agent out of the CPU core. The opcodes were always the fun part. Let it write the menu screens.
October 31, 2026 at 3:48 PM
Reading assembly is a dying art. Between decompilers like Ghidra and AI that can rewrite binary into C, are you actually looking at opcodes anymore, or are you just auditing high-level abstractions? What's your workflow when the symbols are stripped? #ReverseEngineering #Infosec
October 31, 2026 at 11:00 PM
Meine if() sind zu Opcodes mutiert, Hot-Swappable. Je nachdem, wie weit ich das jetzt treribe, geht das Richtung Verzweigungs-Logik in ECS-Architekturen als Hardware-Emulation/Virtual Machine Instruction Set. Das ist weit weg von dem, was man in OOP-Lehrbüchern findet.
October 29, 2026 at 7:21 AM
I just looked at the 6800 table of how instructions + addressing modes are mapped to opcodes. That's a very tidily done arrangement!

Although to be fair, the 6800 doesn't have anywhere near as many addressing modes as the 6502.
October 29, 2026 at 10:47 AM
We had to modify TCM to get the CPU side changes to work.

So the bump mainly comes from changes as to how we handle the opcodes (we have implemented dynamic batching). But w/o the TCM changes, that would have not been possible. Since that code lives in TCM.
October 29, 2026 at 3:29 PM
Look at how the 6502 instructions map to opcodes; there is only space for the 8 accum. instructions (LDA,STA,ADC,SBC,AND,ORA,EOR,CMP) without breaking the pattern. Adding ADD, SUB would only be a few transistors extra in the ALU, but many more transistors in the decode logic as the pattern is broken
October 27, 2026 at 4:00 PM
much improved performance! how many new opcodes did it take?
October 27, 2026 at 3:59 AM
It's all machine opcodes and punch cards for this guy. Don't want to be reliant on "automated systems" like "assemblers" and "compilers", that's "cheating"
Then I'm sorry but uh
Maybe it's not for you?

You are not only cheating the system, but also yourself. Becoming reliant on automated systems to produce your own creativity. Have fun i guess but its nothing id ever want to touch.
October 25, 2026 at 4:15 AM
I caved and started implementing the necessary opcodes.
It's still running on the CPU and not yet RDP accelerated but a far cry from the previous 1 FPS

There's currently an N64 water competition. While it's doubtful I'll win, it'll still be an interesting entry.
October 26, 2026 at 3:54 PM
October 25, 2026 at 7:36 PM
Imagine if this could be optimized (even if it takes additional opcodes and a modified VM to optimize it).

Add a nice little library of SCUMM scripts and some decent examples and voila, we got ourselves a Net Yaroze for all kinds of retro consoles
October 26, 2026 at 4:49 AM
📌 Black Hat Presentation Highlights Security Risks in Python's Pickle Serialization and Introduces Saf... https://www.cyberhub.blog/article/27356-black-hat-presentation-highlights-security-risks-in-pythons-pickle-serialization-and-introduces-safer-pickle-tool
Black Hat Presentation Highlights Security Risks in Python's Pickle Serialization and Introduces Safer Pickle Tool
The Black Hat presentation titled *Deal With It* explores security risks in Python’s *pickle* serialization format, widely used in AI/ML and data science for sharing datasets. Presenters George Litvinov and Andrew Johnston, both Google security engineers, demonstrate how unpickling untrusted files enables arbitrary code execution via the *reduce* opcode, which can invoke functions like *os.system*. They evaluate open-source pickle scanners, revealing bypass techniques such as invalid opcodes, nested pickles, and string reconstruction to evade detection. Their tool, *Safer Pickle*, addresses these gaps with a two-tiered architecture—emulating calls with dummy modules and performing opcode-level analysis—while allowing customizable allow/deny lists. The tool achieves ~10 MB/s scanning speed and integrates with VirusTotal, though the presenters emphasize that *pickle* remains inherently unsafe, recommending alternatives like *safe tensors*. Key takeaways include tailoring security solutions to specific environments and avoiding over-permissive allow lists. The project is open-source on GitHub under *Google/safer-pickle*.
www.cyberhub.blog
October 27, 2026 at 4:37 PM
I still wanna find a way to speed it up without breaking the codebase.

Maybe some additional opcodes and an #ifdef/#else inside the SCUMM script.

Would just be neat if I could find a way to port this to Sega Saturn, N64, PS1, 32X or Atari Jaguar. Or even SNES with SuperFX.
October 26, 2026 at 4:27 AM
On engines that support these opcodes, mono PAL-0 is initialized to all zeros, and are solid black. The only game that seemingly has these specific mono opcodes is Colonel's Bequest, which does have the bytes to *attempt* to set palettes 1–3, but those seem to be ignored by the interpreter, afaict
October 22, 2026 at 11:20 PM
So the opcodes in question are extended SCI0/SCI01 opcodes, and there are 5 of them:

0xFE02 : Set the mono specific dither palette mapping (the engine only seems to support pal 0)
0xFE03 : Draw to the mono buffer, using the pal lookup
0xFE04/06 : Stop drawing
0xFE05 : Draw to the mono, no lookup
October 22, 2026 at 11:20 PM
Who needs C when you can write opcodes by hand
I respect my computer so much I talk to it in its native language.
October 22, 2026 at 4:49 AM
I ended up doing some more research yesterday and ended up rewriting the core of my decoder/encoder to better handle low-level op codes. But, I'm starting to feel like I have a better handle on what these opcodes actually do, what they were intended to do, and how they are implemented
oh yea! FUCK YEA, even! okay, now we are getting somewhere... The first image is with nothing initialized, the second is with a stolen payload from the original PIC.077 and the last one is filled with all the same value 0x01.

HUGE!
October 22, 2026 at 11:20 PM