shut up and taste the rainbow
Notices by :brdRobe: (cr0w@infosec.exchange)
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Wednesday, 01-Jul-2026 04:44:28 JST
:brdRobe:
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Tuesday, 30-Jun-2026 06:50:30 JST
:brdRobe:
@mattly In that case, I would say your best bet is to look for a Netflow setting somewhere. I don't do much with home routers so there may not be one but it's worth a look.
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Tuesday, 30-Jun-2026 06:39:28 JST
:brdRobe:
@mattly Do you have root access on the router?
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Wednesday, 17-Jun-2026 05:32:48 JST
:brdRobe:
@soatok Not just Trump but yes.
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Wednesday, 17-Jun-2026 05:30:30 JST
:brdRobe:
RE: https://cyberplace.social/@GossiTheDog/116759868416707730
CSAM generation is now openly "critical for national security." So yeah, America is going about as expected.
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Friday, 12-Jun-2026 06:47:29 JST
:brdRobe:
@mattly Did you tell them that it wouldn't be as fun that way or what?
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Friday, 12-Jun-2026 06:41:10 JST
:brdRobe:
Like, have y'all tried just not being so vulnerable? Maybe try that and see if the breaches stop.
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Wednesday, 10-Jun-2026 09:48:12 JST
:brdRobe:
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.
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Wednesday, 10-Jun-2026 08:02:18 JST
:brdRobe:
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.
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Tuesday, 09-Jun-2026 09:40:17 JST
:brdRobe:
It's not arson, we're vibe hunting for dinner.
In conversation from infosec.exchange permalink Attachments
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Friday, 05-Jun-2026 06:51:55 JST
:brdRobe:
@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.
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Friday, 05-Jun-2026 06:47:34 JST
:brdRobe:
That whole GitHub breach sure got quiet fast.
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Friday, 05-Jun-2026 05:51:29 JST
:brdRobe:
Reminder: Security companies exist to protect the wealthy. Community protects community.
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Friday, 05-Jun-2026 00:55:57 JST
:brdRobe:
@darfplatypus It's not. I'm a dummy and not blissful.
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Friday, 05-Jun-2026 00:55:56 JST
:brdRobe:
@tehfishman @darfplatypus Okay but also see
In conversation from infosec.exchange permalink Attachments
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Thursday, 04-Jun-2026 23:54:04 JST
:brdRobe:
@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
In conversation from infosec.exchange permalink Attachments
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Wednesday, 03-Jun-2026 12:52:29 JST
:brdRobe:
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.
In conversation from infosec.exchange permalink Attachments
-
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Saturday, 30-May-2026 02:08:34 JST
:brdRobe:
The amount of bluetooth shit being added to critical infrastructure systems in this the year of our cryptid 2026 is extremely concerning.
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Saturday, 23-May-2026 07:55:37 JST
:brdRobe:
@nyanbinary Ask CatSalad. They figured it out.
In conversation from infosec.exchange permalink -
Embed this notice
:brdRobe: (cr0w@infosec.exchange)'s status on Friday, 22-May-2026 04:19:04 JST
:brdRobe:
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.
In conversation from infosec.exchange permalink Attachments