Zero click, silent, remote Android DoS

(smsofdeath.com)

56 points | by MarkBlah 2 hours ago

12 comments

  • nubinetwork 2 minutes ago
  • dmitrijbelikov 4 minutes ago
  • tompagenet2 32 minutes ago
    The Google Issue Tracker link [0] on the site shows access denied for me. Not sure if this is due to it being reappraised or because I specifically don't have access

    [0] https://issuetracker.google.com/issues/509520497

  • est 1 hour ago
    I remember there was a tel: link than when I clicked it wipes everything on my samsung phone
    • latexr 5 minutes ago
      That’s insane, and I’d like to know more about how that even came to pass. A quick search isn’t surfacing anything relevant, do you have a link?
  • grandfunction 43 minutes ago
    This is going to cause absolute havoc. I hope carriers move fast to block this payload.
  • soltanov 28 minutes ago
    Golden Era of AI exploits began few days ago. Close the doors, otherwise you will get cooked.
  • yellow_lead 1 hour ago
    > The attack is remote, needs only the victim's number, and shows them nothing.

    err, how can I send an SMS like this? Would a mobile network even accept/forward such an SMS?

    Little hard reading through the vibe slop here

    • rustyhancock 54 minutes ago
      Looks like the website offers an APK.

      But not all SMS are text messages for the user.

      • snitch182 36 minutes ago
        carriers can reset access points via messages for example. Learned it the hard way when my 1st grader suddenly had internet...
        • LtWorf 6 minutes ago
          I think you need better network equipment at home.

          My provider had given me a remotely managed router. It was trivial to change the configuration and have it work normally.

  • klhs 1 hour ago
    How could they possibly give this a "won't fix" if it can do what is reported here?
    • anonymous908213 37 minutes ago
      The "if" is doing a lot of heavy lifting. Can it do what it claims to do? LLMs are always hallucinating that they've found the most severe bug in software history.
    • MarkBlah 1 hour ago
      mind boggles, issue is they're swamped with AI slop and high number of findings, they're using AI assistance operated by a 3rd party to handle researcher submissions so many legitimate findings slip through the cracks.
      • coldfloor 3 minutes ago
        Ironic comment from someone who literally just submitted an AI slop report and went so far as to give it a website and cutsey name to attempt to feign legitimacy and skill behind the "researcher."
      • klhs 58 minutes ago
        That's unfortunate. They need to do some kind of triage then, I hope this doesn't mean that they're constantly busy now with equally bad or worse bugs, but I guess it wouldn't be too surprising.
  • villgax 1 hour ago
    Shouldn’t click this reminder
    • MarkBlah 1 hour ago
      feel free to curl it, or review the repo https://github.com/MarkBlah/smsofdeath/
      • pogue 33 minutes ago
        01 06 88 80 80 80 00 BE → sent as a data SMS to port 2948

        I'm not familiar with WAP Push and how it works, but is it possible to disable it or block that port on a non-rooted phone?

  • 0xcrypto 1 hour ago
    Can we stop vibecoding a new website for every next vulnerability we find please? Thank you.
    • solyin 1 hour ago
      Blame heartbleed for the practice, which long predates ChatGPT and vibecoding. Human psychology is to blame. Only nerds are going to find CVE-2014-0160 triggering, but if I say heartbleed everyone who was there remembers.
      • autoexec 1 hour ago
        > Only nerds are going to find CVE-2014-0160 triggering, but if I say heartbleed everyone who was there remembers.

        That has more to do with the severity of heartbleed than the fact that it had a name and a logo. I've since seen a lot of vulnerabilities try to market themselves with websites, cute names, and stupid logos but I still don't remember them because they still just weren't big enough to actually be memorable.

    • rustyhancock 52 minutes ago
      I think it's a good idea when there is no CVE and a don't fix status.

      Before this practice in general you simply released the exploit and see if enough chaos triggers a fix.

      • exploderate 30 minutes ago
        If people can't be responsible, let's just create a mailing list, call it "full-disclosure" and post everything there.
    • __m 1 hour ago
      Why? I like the presentation.
    • MarkBlah 1 hour ago
      agreed, we should all use gopher and block all web traffic, go back to text based systems, use single threaded operating systems and use token ring NIC's
  • EdwardDiego 1 hour ago
    Omfg I am interested in this, I'm interested in wtf a WAP push is, but all I'm getting on this website is Claude-speak "not this, but that" and tables of irrelevant numbers, because Claude fucking loves a table.

    Look at this Claude shit:

    > Zero-click. The victim does nothing. No tap, no open, no notification.

    > Silent. Nothing appears in Messages; the attacker's number is never shown.

    Congrats, now you sound like yet another AI YouTube advertisement. "You control when we... ...woohoo"...

    OP, please, if you think you have important information, please write it up yourself, I am so sick and tired of being sent LLM generated Markdown files with zero human input, and now you're just publishing that on a website.

    FFS.

    Oh you had Claude publish your name presumably so you'd get credit for "your" "discovery".

    Mark Blaszczyk, please do better.

    • coldfloor 5 minutes ago
      >...which is the exact shape of a "Destructive Remote DoS" in the VRP's own rules.

      The trend of Claude referring to everything as having a "shape" irrationally annoys the hell out of me. What an absolutely idiotic way to say "X is like Y."

    • hard_times 28 minutes ago
      are you ok?