So this person went ahead and depopulated a Nintendo Switch Lite PCB, soldered a wire to each pad that had a component and then ran a program to determine what is connected to what. To make the result usable, they took a 6000dpi photograph and made the result available as a boardview file. I know nothing. https://usoldering.com/switch-lite/#pcb#reverseengineering
Hacking a Philips toothbrush head to allow you to use it beyond its normal lifetime. Yes, the toothbrush head is hackable. This is a fantastic tale of reverse engineering. Be sure to read the followup at the bottom of the article.
🦀 Small Rust reversing tip: The Rust standard library documentation hides a lot of fields and items by default. For example, the documentation for the struct std::vec::Vec does not show you what a Vec's internal fields are. This can be annoying if you're looking for the implementation details of a certain type - I found that I kept having to click the "source" button on every single struct I wanted to get more information about, to look at the source code directly.
pub struct Vec<T, A = Global> where A: Allocator,<br></br>{<br></br> buf: RawVec<T, A>,<br></br> len: usize,<br></br>}<br></br>
This version of the documentation also documents some items which are hidden from the regular documentation (i.e. items marked as #[doc(hidden)]). One example iscore::panic::panic_info::PanicInfo::internal_constructor, which is an implementation detail of core::panic::panic_info::PanicInfo.
Having the hosted https://stdrs.dev/ site is handy for quickly looking up certain standard library structs, but you can also generate the same information locally with rustdoc, via the --document-private-items and --document-hidden-items flags. The script used to generate the stdrs.dev site is here, and you can tweak the version of the standard library docs you want to generate as required (stdrs.dev has the nightly docs). There are some more details about the site from the author's initial Reddit post about it.
🦀 Have you been noticing that over the past two years, there seems to be more and more malware written in Rust? Have you ever wished there was one page that collected all these malware families and samples in one place, so that you could practice your Rust reverse engineering?
I have collected information about every Rust malware family that I could find, and scoured public malware repositories to find at least one public sample that is available for each family. Download links are provided for each sample to MalShare or Malware Bazaar, neither of which require an account for you to download the samples.
I hope that this can help reversers get a better understanding of Rust binaries, and improve the state of the art in Rust malware reversing. We have a long way to go 😅
Please send a pull request if you notice something is incorrect or missing! Happy reversing!
As many have already heard last week, Dragos had to let go about 50 people. Tuesday last week was my last day on the job, and as of today I am slowly beginning my search for a new role while allowing myself plenty of time to unwind between roles (for a change).
My role at Dragos was to reverse engineer ransomware and I would love to continue reverse engineering malware (not just ransomware) in the future. I've worked in a few different threat intelligence roles over the last several as well.
I'm located on the US East coast and am currently looking to stay remote as relocation and travel are not an option for my family.
Any leads are appreciated! My LinkedIn profile can be found at the top of my profile as well.
@verdre published his work about reverse engineering Android app support in Sailfish OS and bringing it to GNOME/Linux mobile. :android: :gnome: :linux: 📱
The palace rooms from the intro now render pixel-perfectly, aside from the main characters.
The ready room uses only sprites, but Lady Jessica's and Duke Leto's rooms use polygons and line drawing. The gradient-filled polygons incorporate a random number generator to provide some dithering, and the line drawing code supports stippling.
The attached video shows the rooms being drawn piece by piece.
There are some popular #reverseengineering projects for #retrogames whereby the binary is completely disassembled, documented, and ported to a modern compiler or assembler for maintainability.
Sometimes games get quality of life improvements. Sometimes these are bugfixes sometimes they're more than that. What kinds of QOL improvements do you like to see the most? What kinds of QOL improvements go too far?
I got a question on tumblr about Android reverse engineering so I dumped a small pile of resources, which may be useful to anyone looking to start in this area:
I reverse engineered the globe rendering code a good while ago, and finally decided to integrate it into the engine.
There's a couple of lookup tables, some pre-calculation, and a bit of 16.16 fixed point math. Luckily reverse engineering it doesn't mean you have to understand how it works!
This video also highlights the need for a rescaler from the non-square pixels of 320x200.
🦀 🧵 Rust reversing thread: Let's use panic metadata embedded inside Rust binaries to help us reverse engineer!
If you've ever looked inside the strings of a Rust binary, you may have noticed that many of these strings are paths to Rust source files (.rs extension). These are used when printing diagnostic messages when the program panics, such as the following message:
thread 'main' panicked at 'oh no!', srcmain.rs:314:5<br></br>
The above message includes both a source file path srcmain.rs, as well as the exact line and column in the source code where the panic occurred. All of this information is embedded in Rust binaries by default, and is recoverable statically!
Examining these can be useful in separating user from library code, as well as in understanding functionality. This is especially nice because Rust's standard library and the majority of third-party Rust libraries are open-source, so you can use the panic strings to find the relevant location in the source code, and use that to aid in reversing.
🔍 Beginner-Friendly Reverse Engineering Training – Starts February 10th!
In the week of February 10-17, I'll give a remote, beginner-friendly reverse engineering course in cooperation with @ringzer0 This online class is a comprehensive journey into binary program analysis, starting from the absolute basics of reverse engineering, progressing through data type reconstruction, and extending to C++ reverse engineering, malware analysis, and automation techniques.
Key Learning Objectives:
🚀 From Basics to Advanced: Learn reversing from scratch and understand the layers between machine code and high-level languages.
🛠️ Tool Mastery: Become proficient in using IDA, Ghidra, and GDB.
🧩 Code/Data Reconstruction: Learn to reconstruct complex code and data structures from machine code, up to reconstructing C++ class hierarchies.
🕵️ Malware Analysis: Gain strategies for analyzing complex binaries, such as nation-state malware samples.
✋ Hands-On Experience: Practical sessions to strengthen your reverse engineering skills.
Who Should Attend?
Ideal for cybersecurity experts, malware analysts, and forensic specialists looking to delve into reverse engineering and low-level program analysis.
Game Boy Advance schematics now available thanks to Reverse Engineering (lemmy.ml)
Reversed GBA PCBs on github!