zlacker

[parent] [thread] 8 comments
1. dlcarr+(OP)[view] [source] 2025-09-28 16:19:49
Not at all, that piece described a supply chain attack replacing a component with a look-alike part analyzing tens to hundreds of gigabits if data, in a form factor so small that it wouldn't be physically possible without semiconducting fabricating processes years in advance of what existed at the time.

What this article is describing is something far more likely— a firmware attack that doesn't require specialized hardware.

replies(3): >>bri3d+l5 >>WillPo+ra >>timsch+DL1
2. bri3d+l5[view] [source] 2025-09-28 16:53:21
>>dlcarr+(OP)
Wasn’t the implant supposedly (illogically) implanting custom BMC firmware? This actually always struck me as a somewhat unbelievable part of the story: why install a hardware implant when you could just clip the flash chip and implant something without a physical trace?
replies(2): >>wmf+U6 >>dlcarr+wc1
◧◩
3. wmf+U6[view] [source] [discussion] 2025-09-28 17:05:22
>>bri3d+l5
Flash can always be reflashed (you'd lose the implant if the customer does any firmware update) but a separate implant chip can remain infected forever.
replies(1): >>bri3d+Jf
4. WillPo+ra[view] [source] 2025-09-28 17:31:05
>>dlcarr+(OP)
FWIW, the claim in the Bloomberg article was never validated, no one pulled a Supermicro server that had the supposed components. Zero proof since the story was published in 2018 that it wasn't nonsense.
replies(2): >>b112+Sl >>rcxdud+hR
◧◩◪
5. bri3d+Jf[view] [source] [discussion] 2025-09-28 18:10:39
>>wmf+U6
That’s fair - the first thing I’d put in my implant firmware would be a fake firmware updater, but I suppose trading guaranteed persistence for physical detection would be a reasonable tradeoff in some places.
◧◩
6. b112+Sl[view] [source] [discussion] 2025-09-28 18:58:20
>>WillPo+ra
Including Amazon, Meta or whomever else was mentioned in that article, all saying "What? That never happened". There's little reason to cover up the discovery of something like this, from an end-user perspective.
◧◩
7. rcxdud+hR[view] [source] [discussion] 2025-09-28 23:00:02
>>WillPo+ra
Yeah, it was a pretty bizarre story, given it's the kind of thing that definitely happens (though probably through more straightforward just tampering with the firmware), that it was very specific and yet all the details failed to add up.
◧◩
8. dlcarr+wc1[view] [source] [discussion] 2025-09-29 03:46:53
>>bri3d+l5
The Bloomberg article specifically mentioned the attack occurring through the addition of extra hardware:

    “In early 2018, two security companies that I advise were briefed by the FBI’s counterintelligence division investigating this discovery of added malicious chips on Supermicro’s motherboards,” said Mike Janke, a former Navy SEAL who co-founded DataTribe, a venture capital firm. “These two companies were subsequently involved in the government investigation, where they used advanced hardware forensics on the actual tampered Supermicro boards to validate the existence of the added malicious chips.”
9. timsch+DL1[view] [source] 2025-09-29 11:12:03
>>dlcarr+(OP)
> with a look-alike part analyzing tens to hundreds of gigabits if data, in a form factor so small that it wouldn't be physically possible without semiconducting fabricating processes years in advance of what existed at the time.

I'm not sure where you got that idea. The article describes a tiny microcontroller, attached to the read pins of the BMC's boot flash, flipping a few bits in transit from the flash ROM to the BMC SoC as the BMC boots. This is not only practically possible, it's very similar to the technique used to hack the original Xbox and by many console mod chips. And is sufficient to boot the BMC in a vulnerable state for the next chain of an attack.

Nothing about the exploit claimed in the article was impossible or even novel.

That said, I'm not aware of any physical boards found to have the compromised hardware outside of those Bloomberg claim to have witnessed.

[go to top]