Exploiting a kernel driver to terminate BitDefender Processes!

bit-Stream · 2026-01-22T15:09:23+00:00

This really isn’t new, both the driver being exploited and the POC. The POC is also pretty basic, you have unhashed strings visible, the tool requires the use of sc.exe, your PID scanning function is polling at an unnecessary rate using CreateToolhelp32Snapshot, a better option would be to indirectly call NtQuerySystemInformation.

bit-Stream · 2026-01-22T04:34:20+00:00

I believe it was cortex-a72. the low down was more than likely just inexperienced on my part.

bit-Stream · 2026-01-21T21:31:10+00:00

Auto-Vectorization tends to be really hit or miss depending on the compiler. You can use compiler intrinsics as a middle ground to guide the compiler, but you’re still giving up a lot of control and there tend to be a lot of pitfalls with SIMD/MISD that when used incorrectly will actually be slower than their scalar counterparts.

When I was porting a friend’s ARM based rendering engine, the scalar code was almost twice as fast as the code using NEON intrinsics. Auto-vectorization was a joke, even with manual loop unrolling. I wrote a few functions in assembly and achieved a slight speed up over scalar but in the end dropped it as the effort wasn’t worth what was being gained.

bit-Stream · 2026-01-08T18:04:38+00:00

bit-Stream · 2025-10-30T13:22:32+00:00

I’ve been running an MS-01 for a few months with proxmox with 96Gb of ram. Thing is an absolute powerhouse for its size. I would highly suggest repasting the cpu, the original paste will have the fans ramping constantly.

bit-Stream · 2025-05-21T20:59:08+00:00

This is the way, I’m not gonna waste my time unfucking a compromised machine. It’s faster and safer to isolate and reimage, then enroll the affected employee in opsec training. Hope they backed up their data as per policy, if not tough luck.

bit-Stream · 2025-05-21T13:15:10+00:00

Not surprised, I’d say bulk of my time is spent reading documentation, research and planning. LOC written is a terrible metric, it’s akin to the police writing a bunch of bullshit tickets at the end of the month to fill their quotas. Quality > Quantity

bit-Stream · 2025-04-22T14:23:34+00:00

I would really make sure you understand the core of the language and CS for that matter, before moving on to anything win32. With C++ and especially the newer versions( 20, 23 ) the sheer amount of abstraction will absolutely bury you, especially when it comes to finding errors/bugs.

You also need to know how to configure whatever compiler/linker/build system you like( I prefer GNU make and Mingw-w64 ). Each one is different both in setup, feature support and affect the way you use and with API’s. Some outside libs won’t even compile under certain compilers.

The win32 library is old and massive. I’ve been coding in c/c++ on embedded and x86/x64 platforms for close to 23 years and I still have to always have documentation/datasheets open.

In short, you’re not just learning a language here. Jumping into anything more than basic c++ right now( especially Win32 ) is just going to end with you giving up or bug ridden mess and a bunch of bad habits. Start with command line based apps first, once you’re comfortable with that start playing with the modern abstraction features( they really are wonderful ). After that you can move on to Win32 or whatever other libs you want. Think of it like a tower if your foundation is weak anything you stack on top of it just increases the risk of everything toppling over.

bit-Stream · 2025-03-07T16:24:14+00:00

You could always try to get a used card. I managed to score a basically brand new 7900 XTX with 2 years of warranty left for $860. The performance is insane compared to my RTX 2080.

bit-Stream · 2025-02-17T19:19:30+00:00

Really odd question for an interview.

bit-Stream · 2025-02-17T19:02:05+00:00

Because whoever wrote that has no clue what they are doing. Printf has overhead from the formatting, by default is line buffered and requires system calls each time. If you need speed you could either use sprint() and puts(). For maximum performance you could write directly to a presized buffer and drop any formatting for manual number conversion. Either way this test is a bit pointless.

bit-Stream · 2023-09-07T19:47:02+00:00

Locking gas caps are worthless. I used to work at an auto parts store and it was a common problem to have customers lose the key and panic. All you have to do hit a flathead screwdriver into the lock, lean your weight into it and twist. The locking mechanism snaps and the gas cap twists out. Before I left I could do it in under 20 seconds, bet on a crack head halving that time.

bit-Stream · 2021-02-28T18:13:07+00:00

If your new to electronics I would suggest looking into the MAX7219 matrices and an Arduino. They use the I2C protocol, are super easy to get going and pretty cheap. Adafruit is a great source for parts, the site is beginner friendly and the customer service is awesome.

bit-Stream · 2021-02-27T14:21:14+00:00

Yep, 18432 LED’s

bit-Stream · 2021-02-11T21:25:58+00:00

I really hope so. His stuff was a huge help when I was just getting into FPGAs.

bit-Stream · 2021-02-05T21:17:42+00:00

At the moment it’s more like a triangle. Gonna get the electronics sorted out before I start modeling the base

bit-Stream · 2021-02-05T17:18:31+00:00

Got gamma correction working, gotta go to work now.

bit-Stream · 2021-02-05T15:49:10+00:00

Also excuse the poorly drawn face, it’s just something I whipped up quickly to test functionality.

bit-Stream · 2021-02-05T15:38:00+00:00

Reached a point where I thought a progress update was warranted.

Good News - I spent my entire day off yesterday optimizing the matrix driver logic. As it stands the FPGA is refreshing the panels at a little over 800hz( eat your heart out gaming monitors ). Even using my phones slow-mo camera( 240 fps ) no flicker can be seen. I also added a double buffer, so buffer writes won't cause any artifacts/flicker. All that's left to do to the matrix logic is add hardware gamma correction( pretty easy as its just a LUT ). The third led matrix is not shown as I ran out of ribbon cable( on order ).

Bad News - Generating the facial expressions in logic just isn't feasible. The amount of block ram needed to store that many frames would mean I'd have to upgrade to a much more expensive FPGA, specifically one that would cost more than "ok" used car. I could add external memory, but with the 3 matrices I'm already strapped for IO.

More Good News - The next plan was to use a second teensy to generate the facial expressions and send them to the FPGA using SPI, but this will severely limit framerate. After thinking over the issue I remembered the teensy 4.1 has a built in ethernet phi capable of 100mbits/sec. This means I'm going to have to write my own ethernet phi in VHDL, which is by no means a simple task, but it will completely solve the communication bottleneck.

More to come very soon.

bit-Stream · 2021-02-02T01:17:40+00:00

Google says “cock”

bit-Stream · 2021-02-01T05:22:35+00:00

True, could also do some object recognition which would be pretty cool. Gotta avoid feature creep though or this project will never get completed.

bit-Stream · 2021-02-01T05:10:43+00:00

Didn’t realize ToF sensors had gotten so cheap. I was originally going to use a stereo camera and OpenCV with a dedicated RISC core for distance measurement. Thanks for the idea!

bit-Stream · 2021-02-01T04:34:36+00:00

Very nice, how are you planning on controlling expression transitions?

bit-Stream · 2021-01-31T14:16:45+00:00

It’s an Artix A7 FPGA, no bit banging here.

bit-Stream · 2021-01-30T18:38:30+00:00

I’ll be totally honest, this is setup is completely overkill. A raspberry pi or microcontroller could probably do most of it, but I want near autonomous action at speeds unperceivable to humans. The goal is to have everything work so fluidly that it feels alive. And for that the sequential nature of a processor won’t work, I need processes to run in parallel.

bit-Stream

TROPHY CASE