throwaway_account_67

[throwaway_account_67 @67_throwaway]

@lizardmanisback @C2IRIS @0day_ninja @xoreaxeaxeax I think he meant the original makers publicly posting it, vs other's work.
But then again we would never get that for IME/PSP etc soooo 🤷‍♂️

[throwaway_account_67 @67_throwaway]

@cyb3rops Whoever pulled ts should have that engraved into their Resume.😒

[throwaway_account_67 @67_throwaway]

@flyingpassword I have, also I have used the various "House" techniques for Linux. It really isn't harder than Chrome.

[t3tra # type: ignore @t3tra_x]

以前見つけた macOS のカーネルパニックなんだけど, Apple に報告したら「バグじゃないお（ ＾ω＾）」って言われたので public にしておきます

> Deterministic Kernel Panic (NULL Pointer Dereference) via Race Condition in IOTimeSyncClockManager
https://t.co/uaEuXNxClr

[International Cyber Digest @IntCyberDigest]

‼️🚨 BREAKING: Another researcher skipped coordinated disclosure entirely and dropped a critical 1-click GitHub token theft in public because he doesn't want to deal with MSRC. In his own words: "I really don't want to deal with MSRC on VSCode bugs."

The bug: just clicking a link can hand an attacker a GitHub token that reads AND writes to all your repos, including private ones. It lives in github[.]dev, GitHub's browser-based VSCode editor, which passes the browser an OAuth token that isn't scoped to a single repo. That token can touch everything you can.

Researcher Ammar Askar found that VSCode's sandboxed "webviews" leak keyboard events to the main editor. A malicious repo opened via one link can simulate keystrokes, install a local extension that skips VSCode's publisher-trust check, and exfiltrate your token. He published a working proof-of-concept.

He says when he reports github[.]dev bugs, GitHub tells him they're out of scope and to go report to MSRC, and a prior VSCode bug he reported was silently fixed with no credit. One commenter summed up the mood: "MSRC has turned into Feedback Hub."

[throwaway_account_67 @67_throwaway]

@0day_ninja I think it's a really insecure design as a whole, which is why we've had so many issues that we have.
On the other hand, it would make voltage glitching and other bits even more powerful on it.

[throwaway_account_67 @67_throwaway]

@0day_ninja @C2IRIS https://t.co/Kqh6k6BqD4
@xoreaxeaxeax has done years of Research into this and posted about it. I think recently he did another talk too, I can look for the link if you want.

[throwaway_account_67 @67_throwaway]

@lean0x2f @Hacker0x01 >People are still thinking BB platforms are for the people's benefit, not the company's
Idk how cybersec got baited into normie tier "Companies actually care about us :)" mentality.

[throwaway_account_67 @67_throwaway]

@0day_ninja I assume they mean the malware doesn't do whatever custom obfuscation methods, etc, until there is a report already on the initial malware itself.
(so the methods to unpack it, spot it aren't in the report itself)
I could be completely wrong though.

[throwaway_account_67 @67_throwaway]

@C2IRIS Rest in Peace.
He sounds like a brilliant researcher.

[throwaway_account_67 @67_throwaway]

@RussianPanda9xx Happy Birthday, may you have the finest champagne from the tears of the TA's you report on 👏

[throwaway_account_67 @67_throwaway]

@TristanInSec @alisaesage 100% yes, as someone that has researched both.

[throwaway_account_67 @67_throwaway]

@maskirovka3301 @CIA @PalantirTech @mfa_russia @MFA_China Do you have any IoCs, logs, etc that you could have security researchers analyze?
The video showcases a USB not working but there isn't much to go on, besides that.

[throwaway_account_67 @67_throwaway]

@Behi_Sec >download the most common ones SRC
>get an actually good AI model to organize what it does find, and doesn't
>code some shitty python 3 scripts to cover the gaps, not have the same IoCs as the main tools, etc
Hope it helps, friendo. Sorry it's a bit basic though

[throwaway_account_67 @67_throwaway]

@medusa_0xf Yeah, most BB videos/courses are done by people that have under 10 public findings etc.
(not to say there is only public, but yeah scammers aplenty for BB)

[throwaway_account_67 @67_throwaway]

@Behi_Sec @praetorianlabs Because alot of BB posting is done by people that make all their money through selling courses and other shit, not actual bug hunting.
That or they did a little successful hunting, then quit completely for years just to sell the above stuff.

[throwaway_account_67 @67_throwaway]

@Osint613 They really had to use AI to show some basic pictures being shredded? 🥲

[throwaway_account_67 @67_throwaway]

@encrypted_past @therealshodan it's a m$ employee bro, they don't want to offend their overlord and Master.
Funny enough m$ will gladly fire people with 20+ years working for them though.
😕

[throwaway_account_67 @67_throwaway]

https://t.co/MW4fnItZsc It's been a long time since I've seen this creative of a use for Redstone.