Skip to content
HomeVideosBooksBlogs
AllTop postsTopics
Podcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    WeLiveSecurity

    welivesecurity.com · Company blog · on HN since 2013

    ESET's security research blog, reporting on malware, rootkits, backdoors, and attacks by state-linked groups.

    Visit blogHN submissions
    SecurityHardware & Electronics
    What HN says

    HN links it for malware research such as UEFI bootkits, air-gap breaches, and the Linux/Moose botnet, and for ESET's analysis of WebAPK phishing.

    Stats for nerds
    206HN people shared it
    165linked in comments
    1.9Kstory points
    Jul 2026last shared
    2017people per year2026

    Top posts on HN

    1. 1
      LoJax: First UEFI rootkit found in the wild, courtesy of the Sednit group
      5 people · 391 points · first shared 2018 · 86 comments on HN
    2. 2
      European govt air-gapped systems breached using custom malware
      3 people · 281 points · first shared 2024 · 247 comments on HN
    3. 3
      Bootkitty: Analyzing the first UEFI bootkit for Linux
      2 people · 183 points · first shared 2024 · 82 comments on HN
    4. 4
      An exploit kit hiding in the pixels of malicious ads
      5 people · 144 points · first shared 2016 · 91 comments on HN
    5. 5
      Security researchers identify new malware targeting Linux
      1 person · 135 points · first shared 2024 · 65 comments on HN
    6. 6
      Firefox Under Fire: Anatomy of latest 0-day attack
      1 person · 114 points · first shared 2015 · 42 comments on HN
    7. 7
      Beyond KrØØk: Even more Wi‑Fi chips vulnerable to eavesdropping
      1 person · 97 points · first shared 2020 · 11 comments on HN
    8. 8
      KrØØk: Serious vulnerability affecting encryption of billion+ Wi‑Fi devices
      2 people · 79 points · first shared 2020 · 27 comments on HN
    9. 9
      Jumping the Air Gap: 15 Years of Nation-State Effort [pdf]
      2 people · 76 points · first shared 2021 · 40 comments on HN
    10. 10
      RomCom exploits Firefox and Windows zero days in the wild
      4 people · 63 points · first shared 2024 · 28 comments on HN

    What HN people wrote when they linked it

    • instagibApr 2024

      Air-gapped, the only way to go.

      https://www.welivesecurity.com/2021/12/01/jumping-air-gap-15-years-nation-state-effort/

      There are still several vectors even with the top security clearance procedures. They routinely miss things at security checkpoints.

      “Even a perfect air gap will be vulnerable to a variety of different attack vectors, including (but not limited to) the following:

      Physical compromise: An adversary bypasses physical security and gains access directly to the air-gapped network devices. Physical access is by far the most effective and obvious technique.

      Insider threats: Someone who is part of an organization and has access to air-gapped secure systems intentionally or unintentionally compromises a system.

      Supply chain compromise: A vendor with legitimate access to air-gapped systems unwittingly is compromised and brings infected devices into a network.

      Misconfiguration: Misconfiguration of access controls or permissions allows an attacker to access the air-gapped system through a separate device on the network.

      Social engineering (media drop): If an attacker was able to successfully conduct a malicious USB/media drop and an employee was to use that media within the air-gapped system, the network could be compromised.

      Other advanced tactics: Thermal manipulation, covert surface vibrations, LEDs, ultrasonic transmissions, radio signals, and magnetic fields are among a range of advanced tactics documented and demonstrated by researchers at Ben Gurion…

    • kangabruFeb 2024

      I've been gradually improving my dev setup security over the past few months based on continuous reports like this. Here are things I'm trying out to improve my setup: - Use VSCode dev containers for development [1a]. Once you've created one once then they're quite easy to use and you don't need much Docker knowledge - it just needs to be installed. It's perfect for spinning up web/console apps but I had trouble with other stuff like Flutter and Electron. - Similarly I got familiar with GitHub Codespaces for smaller projects [1b]. I've done live coding in an interview before (where I had to modify a simple Node project) and I would absolutely use containers/codespaces for anything like that these days [2]. You can spin one up straight from any GitHub repo page and they're easy to work with. - Read the OWASP guidelines regularly for things like npm, Node, and Docker best practises. e.g. for Docker use the smallest image you can (Alpine) and use explicit Docker image tags [3]. - Review npm/python packages before installing them using socket.dev - it shows a full dependency security overview for things like env variable access, network calls, supply chain attacks, recent code ownership changes etc. You can also disable postinstall scripts globally as suggested by OWASP [4].

      [1a] https://code.visualstudio.com/docs/devcontainers/create-dev-container [1b] https://github.com/codespaces [2]…

    • keleftheriouJan 2022

      Yeah, they also raised $8M back in 2016: https://techcrunch.com/2016/05/26/adding-a-youtube-integration-ampme-raises-8-million-for-its-app-syncing-phones-into-a-single-speaker-system/

      It seems that advertising didn’t work out, so they turned to in-app purchases in 2018 – roughly when the fake reviews also started.

      On the subscription, it’s harder to cancel than it is to sign up for, like all App Store IAP subscriptions. It really should be possible to easily cancel from within the app itself rather than going to the Settings app – something a lot of people don’t know how to do, unfortunately.

      “It used to be a legit app”: https://twitter.com/lap_felix/status/1480631686413041666?s=20

      On the founder’s previous company: “Wajam: From start‑up to massively‑spread adware” https://www.welivesecurity.com/2019/06/05/wajam-startup-massively-spread-adware/

    • ignoramousAug 2024

      > would have thought the hoops Android/iOS make you jump through to add a PWA would be enough to make people question

      The og article by ESET Security [0] specifically talks about (Android/Chrome-supported) WebAPKs essentially bypassing the usual "untrusted sources" warning, and that even the App Info screen shows Play Store as the origin source for all installed WebAPKs.

      > tricky to teach someone to be tech literate with a moving target

      Not fool proof, but given the IoCs, think it might be best to block all but top 50k domains by default.

      Or, inform users if a domain they've never previously visited asks them to enter anything via clipboard or keyboard.

      [0] https://www.welivesecurity.com/en/eset-research/be-careful-what-you-pwish-for-phishing-in-pwa-applications/ / https://archive.md/29SKK (hat-tip u/ChrisArchitect)

    • nosuchthingSep 2017

      BTC because it's scarce

      BTC isn't really scarce, there's quiet a few newer iterations like Litecoin, Monereo, Ethereum, Dogecoin etc..

      It's also worth noting the supply was minted mainly by miners doing very low difficulty work early on, using basic home computers.

      Satoshi made an intensional design choice to gain control of the supply for a very low cost, exploiting late adopters as bag holders.

      The incentive system for bitcoin mining might of anticipated gaining popularity as time passes and increasing the reward as the network grows, but the system was designed completely opposite of that, at the expense of the masses for the benefit of sending the supply to the mining nodes operating in the first few months.

      https://www.welivesecurity.com/wp-content/media_files/total_bitcoins_over_time_lg.jpg

    • ZakMay 2025

      Most of the time, when apps are caught doing something really shady, they're removed from the Play Store for doing the shady thing. A story wouldn't report that they stopped working because of a policy change, but some of these wouldn't make it into the store now:

      https://www.bleepingcomputer.com/news/security/apps-with-15m-installs-on-google-play-send-your-data-to-china/

      https://www.zdnet.com/article/phantomlance-spying-campaign-breaches-google-play-security/

      https://www.welivesecurity.com/2023/05/23/android-app-breaking-bad-legitimate-screen-recording-file-exfiltration/

      There are also examples of apps using the filesystem to try to detect rooted devices, an invasion of user privacy:

      https://www.reddit.com/r/Android/comments/g6cdl6/apps_have_access_to_your_file_system_without/

    Related

    Binarly Blogbinarly.io22 people

    Another Crack in the Chain of Trust: Uncovering (Yet Another) Secure Boot Bypass

    Binarly Blog
    Company · last shared 2026
    Securelistsecurelist.com368 people

    Operation Triangulation: What you get when attack iPhones of researchers

    Securelist
    Company · last shared 2026
    Duo Security Blogduo.com145 people

    SHA-1 'fully and practically broken' by new collision (2020)

    Duo Security Blog
    Company · last shared 2026
    Avast Decodeddecoded.avast.io26 people

    The fresh smell of ransomed coffee

    Avast Decoded
    Company · last shared 2024
    Sophos Newsnews.sophos.com55 people

    ‘Fleeceware’ apps overcharge users for basic app functionality

    Sophos News
    Company · last shared 2025
    SentinelOne Labslabs.sentinelone.com17 people

    Dell patches 12-year-old driver vulnerability impacting millions of PCs

    SentinelOne Labs
    Company · last shared 2021
    SentinelOne Blogsentinelone.com81 people

    Apple’s macOS Ventura – New Security Changes

    SentinelOne Blog
    Company · last shared 2026
    depthfirstdepthfirst.com16 people

    Casting a Net(ty) for Bugs, and Catching a Big One (CVE-2025-59419)

    depthfirst
    Company · last shared 2026