Forgot your password?
typodupeerror
Desktops (Apple)

MacOS 26.4 Adds Warnings For ClickFix Attacks to Its Terminal App (macrumors.com) 66

An anonymous Slashdot reader writes: ClickFix attacks are ramping up. These attacks have users copy and paste a string to something that can execute a command line — like the Windows Run dialog, or a shell prompt.

But MacRumors reports that macOS 26.4 Tahoe (updated earlier this week) introduces a new feature to its Terminal app where it will detect ClickFix attempts and stop them by prompting the user if they really wanted to run those commands.

According to MacRumors, the warning readers "Possible malware, Paste blocked."

"Your Mac has not been harmed. Scammers often encourage pasting text into Terminal to try and harm your Mac or compromise your privacy...."

There is also a "Paste Anyway" option if users still wish to proceed.

MacOS 26.4 Adds Warnings For ClickFix Attacks to Its Terminal App

Comments Filter:
  • by Powercntrl ( 458442 ) on Saturday March 28, 2026 @09:47PM (#66066944) Homepage

    Back in the day, AOL attempted to address phishing scams by putting a disclaimer at the bottom of IM windows. Something along the lines of "Reminder: AOL staff will never ask for your password or billing information". Problem was, people who were foolish enough to fall for social engineering scams don't pay much attention to those sort of warnings, either.

    Seems like all the scammers will have to do is update their instructions to include "Please disregard the pop-up and click Paste Anyway".

    • by dgatwood ( 11270 )

      Reply "yes", then close and reopen this message to activate the link.

      No matter how idiot-proof you make technology, God will always create a better idiot. That's why the right way to solve this problem is:

      • Make it as hard as possible for users to accidentally do something that is irreversible, and as easy as possible to roll back even serious mistakes. This means, among other things, keeping more than just a single backup. (Apple, I'm talking about your borderline useless iCloud backups here when I say t
      • Reply "yes", then close and reopen this message to activate the link.

        No matter how idiot-proof you make technology, God will always create a better idiot. That's why the right way to solve this problem is:

        • Make it as hard as possible for users to accidentally do something that is irreversible, and as easy as possible to roll back even serious mistakes. This means, among other things, keeping more than just a single backup. (Apple, I'm talking about your borderline useless iCloud backups here when I say that.)

        You don't like Time Machine? I have hourly backups on one drive, and daily backups on a drive I store in a different location.

        I'd never use any cloud backup, that's like asking Jerry Sandusky to babysit a 10 year old boy.

        • by dgatwood ( 11270 )

          Reply "yes", then close and reopen this message to activate the link.

          No matter how idiot-proof you make technology, God will always create a better idiot. That's why the right way to solve this problem is:

          • Make it as hard as possible for users to accidentally do something that is irreversible, and as easy as possible to roll back even serious mistakes. This means, among other things, keeping more than just a single backup. (Apple, I'm talking about your borderline useless iCloud backups here when I say that.)

          You don't like Time Machine? I have hourly backups on one drive, and daily backups on a drive I store in a different location.

          I love Time Machine (except for how slow it is over SMB and how often the disk images corrupt themselves in ways that prevent future backups). Wish it existed on iOS and VisionOS.

      • by ameline ( 771895 )

        With a huge carve out for war crimes, murder, rape, child molestation, sexual assault, and official corruption. Those should live and last *forever*. Otherwise your "Epstien class" will always get away with everything.

  • I can imagine Apple later removing the "paste anyway" option and requiring you to go to Settings > Privacy to confirm the action, like how they've done with running apps downloaded off of the internet
    • by tlhIngan ( 30335 )

      I can imagine Apple later removing the "paste anyway" option and requiring you to go to Settings > Privacy to confirm the action, like how they've done with running apps downloaded off of the internet

      It's a function implemented in the shipped terminal.app. If you use a third party terminal app, it won't have the protection. Chances are if you're using a third party terminal you're probably sophisticated enough to not blindly run shell commands

    • by dub42 ( 992285 )
      I believe that you can just right click and press open. That will let you run the application without going to the settings.
  • If someone can’t type a long command into a terminal without typos, they probably should not be using a terminal for anything other than basic commands anyway.
    • by larwe ( 858929 ) on Saturday March 28, 2026 @10:56PM (#66067018)
      True but useless. For a long complex commandline input, it saves a lot of work to be able to paste it in. Not to mention the possibility that a typo might have undesirable consequences.
      • by Viol8 ( 599362 )

        Anyone who just cut and pastes a string of shell commands from some random web page or email into a terminal without checking them first frankly deserves what they get. If you're this dumb stay away from the command line.

        • by larwe ( 858929 )
          I mentioned nothing about random web pages. In our git repos, there are plenty of internal docs saying "to provision the embedded device, plug it in and run this 200-character commandline". Being able to paste those vs typing them saves a lot of time.
          • And you wouldn't check it first particularly if it had to run as root? Oooookay.

            • by larwe ( 858929 )
              Checking isn't the problem being solved. Sure I check what I run. Being able to check it on the webpage, then cut and paste it, then maybe check again that I cut and pasted correctly - is far less work, and FAR less error prone than having to type it in. Not to mention faster. If I validate it once, I can Ctrl-V multiple times rather than typing it all out again multiple times. Assume that I have sufficient sophistication to insert check steps where appropriate. Blocking me from using a simple memcpy() to d
    • If someone can’t type a long command into a terminal without typos, they probably should not be using a terminal for anything other than basic commands anyway.

      Usually, they'd be copying commands from a website or a manual, in which case the typos should not even exist

  • Can you disable all the safety features on a modern Mac and have it behave like an old school unix box? You know run su and then accidentally do something dumb? I mean we all survived those days.

    • Re: (Score:3, Informative)

      by larwe ( 858929 )
      Current versions of MacOS have something called "System Integrity Protection" which restricts certain directories from being tampered with even in a su'd shell. It can be disabled, but it's a very off-label way to run the OS and the consequences could be ... spicy.
    • Re:Question (Score:5, Funny)

      by Powercntrl ( 458442 ) on Saturday March 28, 2026 @11:19PM (#66067034) Homepage

      You know run su and then accidentally do something dumb?

      I'm pretty sure my Mac will let me run su and then send a text to my ex, but I'm not going to try it.

    • Re: (Score:3, Informative)

      by caseih ( 160668 )

      Yes you can. You have to boot into recovery mode and then change the security level. This is already something you have to do to load third-part (even signed) kexts, which are sometimes required for certain types of presumably poorly written (or not Apple-blessed) hardware drivers.

      Apparently this is even still possible on the iPhone chipped MacBook Neo.

  • Linux is insecure (Score:3, Interesting)

    by TheMiddleRoad ( 1153113 ) on Sunday March 29, 2026 @02:43AM (#66067114)
    Linux is generally insecure: https://madaidans-insecurities... [github.io] What hardening looks like: https://grapheneos.org/feature... [grapheneos.org] Not that all this makes GrapheneOS perfectly secure, but it's much better than standard Linux distros.
    • Linux has served me just fine for three decades. I got rid of my GrapheneOS phone because it constantly got in my way. My threat model does not involve bring pursued by nation state actors, and I don't equate security with having doors slammed in my face all day. Security is not the most important thing in life. Vigilance will serve you much better. As Franklin said, "Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety."

      • Linux has served me just fine for three decades

        Same. But, I can honestly say the same of Windows. Though I never boarded the Mac train, I suspect that the same could be said for that.

        I think it has much more to do with the user than the overall security of the operating system.

      • GrapheneOS is giving up liberty? WTF?
    • Why do you compare GrapheneOS to a standard Linux desktop, instead of to Google Android?

      Obviously, if you take a platform that is geared towards running applications from untrusted sources and compare that to a standard Linux desktop distribution that isn't configure for that, you'll find common desktop Linux lacking.

      On the other hand, does GrapheneOS or Android have a desktop that's halfway usable?

      Historically, Linux got the reputation for being more secure because Microsoft made a number of brain-de

      • For the true paranoid, if you need to sandbox, you're doing it wrong.

        Everyone is doing it wrong, that's why we need to sandbox.

        Even if you were perfect, you wouldn't have time to do everything yourself, so you would still want sandboxing to protect you from the efforts of others.

      • The point is a well-designed, more-secure OS. That is independent of having a desktop or not. Linux runs untrusted apps all the time. Supply chain attacks are brutal, no? For the paranoid, if you're not sandboxing, you're doing it wrong.
        • I actually don't disagree in spirit, it just seems to me that we have different definitions of truly paranoid.

          A colleague of mine with a Windows Linux dual boot machine, games on one side and mail and web on the other, uses a live Linux disc to do e-banking. He's just an informed guy, I wouldn't consider him paranoid at all.

          If you're paranoid or actually in the know that "they" are after you, you have to use different machines for different purposes. I mean, one can trust sandboxes only so far, and if y

          • Interestingly, a live Linux disc can be imperfect too, if something is installed at boot from BIOS, for instance. Even then, I'd want sandboxing on my live linux boot. There is no perfect security. This is clear. Like how Anthropic's Claude just got released into the wild, all after Anthropic was supposed to be the bug squashers of the universe.
            • Agreed on the BIOS infection part. The programs could have been compiled with an infected compiler too. But I don't get why you want sandboxing on your life disc, you mean, inside, to reduce attack surface in case only non essential programs are infected, or running running your life disc in a sandbox, or just out of principle?

              Because with all sandboxing, if your operating system isn't clean it's not going to save you from that attack angle. But I'm convinced you know that.

              • It's another layer of difficulty for an attack to overcome, one that doesn't usually inconvenience the user. Also, attacks installed in BIOS or the OS aren't necessarily done in some overarching god mode. AFAIK, they often install an app that then does the dirty work, and sandboxing would get in the way of that vector.
                • Good point, but would that be equally so if sandboxing were totally the norm? Then every such program would take it into account, right...? I mean, sandboxing just prevents looking sideways, if you're in the lower layers (BIOS, OS) you can look up all the way, or am I missing something?
                  • That's all security really is, though: making the attacker have to do more work.
                    • From a certain angle, exactly. Reminds me of a Dutch friend about how many bike locks are required: one more than the bikes left and right of yours...
    • From your references:

      Windows, which is leaning heavily towards Rust, a memory safe language...

      This tells me that the article is written by a Rust evangelist and nothing they say can be trusted to be unbiased. Furthermore. Windows, more accurately Microsoft is not leaning heavily toward Rust. Microsoft uses very little Rust in Windows and has stated categorically that there is no intent to re-write Windows in Rust. Windows is mostly written in C/C++/C# with the .Net framework and there is no plan to change that.

      • You're some kind of religious zealot? You found the word "Rust" and so everything else is a lie? Microsoft uses Rust where its advantages matter. What's the big deal, snowflake?
  • The prompt is that little $_, or #, or blinking square, etc. showing you where to type. See VT100 terminals. A shell is the commands and features available by default when using that shell on your terminal. Make sure that you let the shell know what type of terminal it is running on. The command line is that space next to prompt, where you can input shell commands, pass through to system commands, or actually act interactively on a more feature-full terminal like a VT320, for example, a menu that allows

  • by PPH ( 736903 )

    These attacks have users copy and paste a string to something that can execute a command line.
    .
    . ClickFix attempts and stop them by prompting the user if they really wanted to run those commands.

    I've seen this on one of my recent Linux installs (Devuan). I get a warning before pasting into a shell prompt. That's not a problem because I know how to inspect text (tiny fonts, etc) copied from an untrusted source before running them*. Unfortunately, it also seems to interfere with the 'copy from terminal' functions. Which makes it a real annoyance.

    *I've caught a few of these. And rather than deleting them, I've tweaked some of the concealed commands to see if I can't have some real fun with the origin

I don't have any use for bodyguards, but I do have a specific use for two highly trained certified public accountants. -- Elvis Presley

Working...