Hacker Newsnew | past | comments | ask | show | jobs | submit | soupdiver's commentslogin

It shouldn't but often still is... and maybe a runbook like this is easier to handle than a script with possibly 1000 lines and not a single comment. Of course, in your ideal world maybe nothing of this applies and you never have any incidents ;)



Begins @ 27:21

In addition contents of the presentation, in terms of timeline...

2018 (September): First undocumented MMIO-present CPU launched, Apple A12 Bionic SOC.

2021 (December): Early exploit chain infrastructure backuprabbit.com created 2021-12-15T18:33:19Z, cloudsponcer.com created 2021-12-17T16:33:50Z.

2022 (April): Later exploit chain infrastructure snoweeanalytics.com created 2022-04-20T15:09:17Z suggesting exploit weaponized by this date.

2023 (December): Approximate date of capture (working back from "half year" quoted analysis period + mid-2023 Apple reports.

The presenters also state that signs within the code reportedly suggested the origin APT group has used the same attack codebase for "10 years" (ie. since ~2013) and also uses it to attack MacOS laptops (with antivirus circumvention). The presenters note that the very "backdoor-like" signed debug functionality may have been included in the chips without Apple's knowledge, eg. by the GPU developer.

So... in less than 3.5 years since the first vulnerable chip hit the market, a series of undocumented debug MMIOs in the Apple CoreSight GPU requiring knowledge of a lengthy secret were successfully weaponized and exploited by an established APT group with a 10+ year history. Kaspersky are "not speculating" but IMHO this is unlikely to be anything but a major state actor.

Theory: I guess since Apple was handed ample evidence of ~40 self-doxxed APT-related AppleIDs, we can judge the identity using any follow-up national security type announcements from the US. If all is quiet it's probably the NSA.


It's really a pity they explain all the mistakes that helped the malware be detected.


It's not, it really isnt. Honestly just apply this mentality to one other scenario to test the waters. We should stop publishing yara rules because it flips our hand to the malware makers? It's nonsense to even say.


The (first?) version of the real recording is now up: https://media.ccc.de/v/37c3-11859-operation_triangulation_wh...


that actually sounds quite neat


> I personally struggle with the 14". It feels too small to be productive on, at least for coding. Anyone else experience this?

absolutely not... working for 10 years on 13/14 and never _felt_ that way I get this is personal ;)


This is about Podman, not Docker


exactly what I thought... there are nowhere 1-2 setences which sum up what they're doing


I can confirm this as I'm living in Berlin :D


Nice article! I also do consultancy in that field and your article describes my work situation by 90%


yeah, this basically confirms my experience and is also what annoys me so much. Not even investing 5s to read the first sentence of the profile... just wasting time for every one.


I actually thought similar after my current experience


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: