Notices by cR0w (cr0w@infosec.exchange)

@mattly Did you tell them that it wouldn't be as fun that way or what?

Like, have y'all tried just not being so vulnerable? Maybe try that and see if the breaches stop.

While it's fun making fun of AI failures, be sure to attribute the failures to the orgs and people responsible, especially when talking to people outside of this bubble. We can't let them keep getting away with blaming it all on AI growing pains and not the intentional business decisions that enabled the failures.

If you have any Palo Alto GlobalProtect portals, maybe take a look for successful authentications from AS215540, especially 92.118.112.230, 89.185.80.144, or 89.185.80.183.

#GAYINT

It's not arson, we're vibe hunting for dinner.

@GossiTheDog I already grabbed that but it's funny how quiet it's been since that listing was published. I'm still hammering it to try to get people to give a fuck about VS Code extensions but it isn't working.

That whole GitHub breach sure got quiet fast.

Reminder: Security companies exist to protect the wealthy. Community protects community.

@darfplatypus It's not. I'm a dummy and not blissful.

@tehfishman @darfplatypus Okay but also see

@christopherkunz @wdormann Here's a new one to take a look at. I haven't gone through it and can't vouch for its legitimacy, but y'all know what you're doing more than I do anyway: https://github.com/Vanquishermacdetach/CVE-2026-41089-509

RE: https://infosec.exchange/@cR0w/116682616422398554

I think what bugs me about this is:

• They don't care.
• It's clearly intentional.
• We all know nothing will change.

The amount of bluetooth shit being added to critical infrastructure systems in this the year of our cryptid 2026 is extremely concerning.

@nyanbinary Ask CatSalad. They figured it out.

EITW ../ in Trend Micro Apex One. :brdAlert:

https://success.trendmicro.com/en-US/solution/KA-0023430

CVE-2026-34926

TrendAI has released updates to Apex One (on-premise), Apex One as a Service and Vision One - Standard Endpoint Protection (SEP) to resolve multiple vulnerabilities.

Microsoft is aware of a security feature bypass vulnerability in Windows publicly referred to as "YellowKey". The proof of concept for this vulnerability has been made public violating coordinated vulnerability best practices.

I know people here probably don't want to rehash the disclosure discussion for the 683,547,329th time, but fuck Microsoft and this passive aggressive bullshit trying to frame their own interests as "best practices" in a vuln mitigation publication. Your shit is getting torn apart. Act like you've been there before because we all know you have.

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-45585

@soatok Hey @ifin what's your email address?

https://gptzero.me/news/investigations/ey

Ernst & Young (EY) Canada published a cybersecurity report on loyalty program safeguards. We chased down every citation. Most were hallucinated.

Shocked. Shocked! Well, not that shocked.

:exclamation_rainbow: catte.exe has encountered an error

RE: https://infosec.exchange/@briankrebs/116597569851456486

BRB, I need more popcorn for that screenshot alone. :blobcatpopcorn: