Product definition

What is BlockBlock?

BlockBlock watches the locations macOS uses for persistence — login items, launch agents and daemons, and the other places software writes itself so it runs again after a restart — and alerts when a new persistent component is added. The alert names the process responsible, with its path and arguments, and offers code-signing information, VirusTotal lookups for both the process and the persisted item, and the process's ancestry. You then choose Allow or Block; either answer becomes a rule, and Block removes the item from the file system so the persistence does not survive. It is built on Apple's Endpoint Security framework, which is why installation needs an administrator authorisation and Full Disk Access. Additional protections cover non-notarised programs, downloaded scripts, and pastes into Terminal. GPL-3.0, free, and developed by Objective-See.

Verified product facts

Type
security utilityEditorially reviewed
Platform
macOS
Pricing
FreeDeveloper-stated
Open source
Yes
Relationship to Nuanyue
Third-party product — not published by NuanyueEditorially reviewed
Licence
GPL-3.0
Current version
2.5.2Developer-stated

Last updated , last reviewed . Facts marked developer-stated come from the developer and are not independently confirmed; editorially reviewed marks a Nuanyue judgement.

Key features

What BlockBlock does at a glance.

  • Monitors common persistence locations and alerts when a new persistent component is added

  • Alerts identify the responsible process

    With its pid, path and arguments

  • Code-signing details, VirusTotal lookups and process ancestry from the alert

  • Allow or Block

    With a rule created from your answer and a choice of rule scope

  • Blocking removes the persisted item from the file system

  • Optional Notarization protection

    For non-notarised programs

  • Optional Block Scripts protection

    For downloaded scripts

  • Paste Protection blocks suspicious pastes into Terminal, with optional heuristics

Common tasks

What you can use BlockBlock for

  • Noticing when something installs a launch agent you did not ask for
  • Reviewing what a newly installed app added to your login items
  • Blocking a persistence attempt and removing the installed item in one action
  • Adding a second opinion to a macOS security setup alongside a malware scanner
  • Stopping a ClickFix-style instruction from being pasted into Terminal
Audience

Who is BlockBlock for?

  • People who want to be told when something establishes persistence, rather than finding out later
  • Users comfortable reading a process path and a code-signing result before answering an alert
  • Anyone who prefers an open-source security tool they can read
Not a fit

Who is BlockBlock not for?

  • People who want a silent background tool — BlockBlock is designed to interrupt
  • Anyone unwilling to grant Full Disk Access and administrator rights at install
  • Users on macOS earlier than 10.15

Limitations

  • Requires an administrator authorisation at install and Full Disk Access, because it uses Apple's Endpoint Security framework
  • Designed to alert on every new persistent component, so legitimate installers also raise alerts — the developer's own FAQ states an alert does not mean you are infected
  • Paste Protection needs Accessibility permission for BlockBlock's helper app
  • The developer documents that a response to a Notarization alert is deliberately not saved across reboots, though it is cached until the next reboot or restart
  • The developer documents a macOS Ventura bug where BlockBlock reports itself inactive despite Full Disk Access, fixed in macOS 13.0.1
  • A minimum macOS version of 10.15 is stated on the product page; individual protections may depend on newer frameworks

Strengths and trade-offs

What BlockBlock does well, and what to weigh before choosing it. Points marked developer-stated come from the developer’s own material and have not been independently confirmed.

Strengths

  • The developer states that BlockBlock monitors common persistence locations and alerts whenever a new persistent component is added, which is the specific behaviour macOS does not surface on its own.Developer-stated
  • Alerts carry the responsible process with pid, path and arguments, plus clickable code-signing information, VirusTotal detections for both the process and the persisted item, and process ancestry — enough to make a decision without leaving the alert.Developer-stated
  • Choosing Block removes the persisted item from the file system, so the answer does something rather than only recording a preference.Developer-stated
  • Rule scope can match on the process, the persistence file, the persistence item, or a combination, rather than a single all-or-nothing rule.Developer-stated
  • Free and GPL-3.0, with the source in a public repository and a published SHA-256 for the download.
  • Beyond persistence monitoring, the developer offers Notarization, Block Scripts and Paste Protection modes, the last aimed at ClickFix-style instructions pasted into Terminal.Developer-stated

Trade-offs

  • It needs administrator authorisation to install and Full Disk Access to run, which is a broad permission for an app that reports on other apps.Developer-stated
  • Alerting on every new persistent component means legitimate software triggers it too — the developer's FAQ says plainly that an alert does not necessarily mean an infection, which puts the judgement on you each time.Developer-stated
  • The extra protections are not free of setup: Paste Protection requires granting Accessibility permission to BlockBlock's helper app.Developer-stated
  • Allow-or-block answers for Notarization alerts are deliberately not persisted across reboots, so the same prompt returns after a restart.Developer-stated
  • The developer documents a macOS Ventura bug where BlockBlock reports itself inactive even with Full Disk Access, resolved only by macOS 13.0.1 or a manual workaround.Developer-stated

Overview

Most malware on a Mac does not need to stay running. It needs to come back. That means writing itself somewhere macOS will execute at login or boot — a launch agent, a launch daemon, a login item.

Those locations are exactly what BlockBlock watches. When a new persistent component appears, it raises an alert and waits for an answer.

What an Alert Contains

The alert is the product, so it is worth describing precisely. It names the process responsible for the action, with its pid, path and arguments, and it offers three things to click: the process’s code-signing information, VirusTotal detections for both the responsible process and the item that was persisted, and the process’s ancestry.

Then you answer. Allow creates a rule; Block creates a rule and removes the persisted item from the file system, which is what actually stops the persistence. Rule scope lets you decide whether the rule matches the process, the persistence file, the persisted item, or some combination — which is the difference between “never ask me about this app again” and “never let anything write to this file again”.

Responses are logged to /Library/Objective-See/BlockBlock/BlockBlock.log.

The Cost of Alerting on Everything

By design it alerts on any new persistent component, and plenty of legitimate software installs one. The developer says so directly in the FAQ: an alert does not necessarily mean an infection, and BlockBlock itself persists so it can keep protecting.

That is an honest design choice with a real cost. A tool that interrupts you trades a moment of your attention for the chance to catch something. If you install software often, you will see it often, and the quality of the outcome depends on whether you read the process path before clicking Allow.

Permissions

BlockBlock uses Apple’s Endpoint Security framework, which is what gives it visibility into these events. Two consequences follow, both stated by the developer: installation requires an administrator authorisation, and the app needs Full Disk Access. The first-run flow walks you through granting it, including the manual path if the app does not appear in the list.

The optional protections have their own setup. Paste Protection, which blocks suspicious pastes into Terminal and can apply heuristics to the pasteboard contents, needs Accessibility permission for BlockBlock’s helper app.

The Additional Protections

Three modes sit on top of persistence monitoring. Notarization alerts when a non-notarised program runs, by default only for downloaded programs. Block Scripts alerts when a downloaded script executes. Paste Protection targets the ClickFix pattern — instructions that ask you to paste a command into Terminal.

One detail worth knowing: the developer states that your answer to a Notarization alert is deliberately not saved across reboots, though it is cached until the next reboot or a restart of BlockBlock. So the same prompt can return.

Who It Suits

People who want to be told when something establishes persistence, and who are willing to read a process path and a signing result before answering. It is a poor fit for anyone who wants a silent tool, and it is not a scanner — it does not look for malware already running, it watches the door.

Questions about BlockBlock

Does an alert mean my Mac is infected?

No. The developer's own FAQ says an alert means a persistent component was added, and that there are many legitimate reasons for that — BlockBlock itself persists so it can keep running. The point of the alert is to make you look, not to declare a verdict.Editorially reviewed

What permissions does it need?

An administrator authorisation during installation, because it uses Apple's Endpoint Security framework, and Full Disk Access, which is a prerequisite of that framework. Paste Protection additionally needs Accessibility permission for its helper app.Editorially reviewed

What happens when I choose Block?

BlockBlock removes the persisted item from the file system, which stops the persistence. Both Allow and Block create a rule, unless you tick the "temporarily" option, and the rule's scope can be limited to the process, the persistence file or the persisted item.Editorially reviewed

Where are my answers recorded?

The developer states that all alert responses are logged to /Library/Objective-See/BlockBlock/BlockBlock.log.Editorially reviewed

Can it stop malware that is already running?

That is not what it does. BlockBlock watches persistence locations and reacts to new components being added. The developer positions it as detection and blocking of persistence, not as a scanner.Editorially reviewed

Is it free?

Yes. It is GPL-3.0, the download is free, and the source is published.Editorially reviewed

Compared with

Head-to-head comparisons Nuanyue has published.

  • KnockKnock

    See what's persistently installed on your Mac.

    Same question, different timing: KnockKnock enumerates what is persistently installed when you ask it, BlockBlock alerts the moment a new persistent component appears.

    • Security
    • Open Source
    • v4.1.0

Works well with

Not a replacement — apps commonly used alongside this one.

  • LuLu

    Free open-source firewall for blocking outgoing connections on macOS.

    Both come from Objective-See and watch a different door — LuLu alerts on new outgoing connections, BlockBlock on new persistence. Neither covers the other's case.

    • Security
    • Open Source
    • v4.5.1
  • OverSight app icon

    OverSight

    Tool for monitoring microphone and webcam access.

    Oversight monitors microphone and camera access while BlockBlock watches persistence; together they cover two separate things software can do behind your back.

    • Security
    • Open Source
    • v2.4.0
  • TaskExplorer

    Explore all processes running on your Mac with TaskExplorer.

    When a BlockBlock alert names a process you do not recognise, TaskExplorer is where you go to inspect what that process actually is.

    • Security
    • Open Source
    • v3.1.0
Get it

Sources

Facts on this page are checked against the sources below. Last updated , last reviewed .

How Nuanyue grades sources →