Work in progress: 82,651 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #3399

B

Binarly

Company blog · binarly.io/blogsecurityhardware

Binarly is the company blog at binarly.io, writing about security and hardware. Since 2022, 22 different Hacker News readers have linked it 23 times, most often “LogoFAIL: Secure Boot bypass with manipulated boot logos”. It is still writing: the last post was on 2026-09-02, and you can follow it by feed.

Visit the blog
23mentions?
22HN people?
2022–2026first – last linked?
Links on Hacker News per year · peak 6 in 2025

Binarly delivers binary-level product security for shipped software and firmware. Product security and engineering teams use the Transparency Platform to inspect built binaries, validate SBOMs and CBOMs, detect tampering secrets and malicious code, prioritize exploitable issues with reachability and

Most-linked posts?

  1. LogoFAIL: Secure Boot bypass with manipulated boot logos
    3 people · 3 mentions · first linked 2023-12-04
  2. Finding LogoFAIL: The Dangers of Image Parsing During System Boot
    3 people · 3 mentions · first linked 2023-12-06
  3. PKfail: Untrusted Platform Keys Undermine Secure Boot on UEFI Ecosystem
    2 people · 2 mentions · first linked 2024-07-26
  4. An In-Depth Look at the 23 High-Impact Vulnerabilities
    2 people · 2 mentions · first linked 2022-02-02

What Hacker News says?

  1. https://eclypsium.com/blog/understanding-detecting-pixiefail... https://binarly.io/posts/The_Far_Reaching_Consequences_of_Lo...

    Comment linking /posts/The_Far_Reaching_Consequences_of_LogoFAIL/

    on “A brief history of the U.S. trying to add backdoors into encrypted data (2016)”
  2. Submitted Another Crack in the Chain of Trust: Uncovering (Yet Another) Secure Boot Bypass as a story · 126 points

    HN discussion
  3. Hello, I am the Bootkitty developer. The reason our bootkit is self-signed is because it uses the LogoFAIL vulnerability to register a MOK on the system to bypass secureboot, which is why our signature is included. I will leave an analysis article about LogoFAIL at the link below. https://www.binarly.io/blog/logofail-exploited-to-deploy-boo...

    Comment linking /blog/logofail-exploited-to-deploy-bootkitty-the-first-uefi-bootkit-for-linux

    on “Bootkitty: Analyzing the first UEFI bootkit for Linux”
  4. Submitted XZ Utils Backdoor Still Lurking in Docker Images as a story · 113 points

    HN discussion
  5. The root of trust in Secure Boot is typically an OEM certificate, not Microsoft's, which is probably even worse: https://www.binarly.io/blog/pkfail-untrusted-platform-keys-u... In any case, you're free to remove Microsoft's certificates and enroll your own.

    Comment linking /blog/pkfail-untrusted-platform-keys-undermine-secure-boot

    on “Microsoft's open source tools were hacked to steal passwords of AI developers”
  6. Submitted An In-Depth Look at the 23 High-Impact Vulnerabilities as a story · 9 points

    HN discussion
  7. there are 3 paths. 1. placing logo into ESP (EFI System Partition) via admin privileges 2. Bios update tool 3. When there is no expected way to customize the logo, it is still possible via physical attack vector: just with an SPI flash programmer if a logo is not covered with any hardware-based Verified Boot technology like Intel Boot Guard or AMD Hardware-Validated Boot “As we can see in the following table, we det…

    Comment linking /posts/finding_logofail_the_dangers_of_image_parsing_during_system_boot/

    on “Just about every Windows/Linux device vulnerable to new LogoFAIL firmware attack”
  8. Submitted 23 high-impact UEFI vulnerabilities affecting multiple vendors as a story · 7 points

    HN discussion
  9. The binarly post[0] (submitted by @skilled 2 days ago /w no comments and little upvote love) is a cleaner source[1] and just as easy to read. This seems to be a bit of a rewrite, bit of a copy/paste (images straight from binarly). The vulnerability was published a week ago, this article implies it was disclosed today. [0]: https://binarly.io/posts/The_Far_Reaching_Consequences_of_Lo... [1]: https://news.ycombinator.…

    Comment linking /posts/The_Far_Reaching_Consequences_of_LogoFAIL/

    on “Just about every Windows/Linux device vulnerable to new LogoFAIL firmware attack”
  10. Submitted PKfail: Untrusted Platform Keys Undermine Secure Boot on UEFI Ecosystem as a story · 5 points

    HN discussion
  11. Submitted PKfail: Untrusted Platform Keys Undermine Secure Boot on UEFI Ecosystem as a story · 4 points

    HN discussion
  12. Submitted Broken Trust: Fixed Supermicro BMC Bug Gains New Life in Two New Vulnerabilities as a story · 3 points

    HN discussion
  13. Submitted FirmwareBleed: The industry fails to adopt Return Stack Buffer mitigations in S as a story · 3 points

    HN discussion
  14. Submitted BeneFITs: Bypassing Signature Verification in U-Boot SPL as a story · 2 points

    HN discussion
  15. Submitted SMM memory corruption vulnerability in SMM module on Gigabyte device/SMRAM write as a story · 2 points

    HN discussion
  16. Submitted Clevo Boot Guard Keys Leaked in Update Package as a story · 2 points

    HN discussion
  17. Submitted UEFI Bootkit Hunting: In-Depth Search for Unique Code Behavior as a story · 2 points

    HN discussion
  18. Submitted Unfit to Boot: Breaking U-Boot's Fit Signature Verification as a story · 1 points

    HN discussion
  19. Submitted Finding LogoFAIL: The Dangers of Image Parsing During System Boot as a story · 1 points

    HN discussion
  20. Submitted Finding LogoFAIL: The Dangers of Image Parsing During System Boot as a story · 1 points

    HN discussion
  21. Submitted LogoFAIL: Secure Boot bypass with manipulated boot logos as a story · 1 points

    HN discussion
  22. Submitted High-Impact Vulnerabilities in Firmware Impacting Millions of Enterprise Devices as a story · 1 points

    HN discussion
  23. Submitted HP Devices – Vulnerabilities in Firmware as a story · 1 points

    HN discussion

Search all of HN for binarly.io

Linked by the same people?