Aikido Endpoint Protection on Mac

Blocks malicious npm and PyPI packages before they install — the endpoint edition of Aikido's SafeChain. Free plan covers two devices. This is an install guard, not antivirus: it doesn't watch running apps or clean an infected machine. Finish the built-in checks on mac.0xosprey.com first; this is layer two.

Before you start

Install

  1. Sign up or sign in at app.aikido.dev.
  2. Open Endpoint Protection → Devices.
  3. Click Connect Device (top right) and choose macOS. The dashboard shows a one-line install script with your enrollment token (AIK_...) already embedded — copy the whole line.
  4. Open Terminal, paste the line, and run it.
  5. The script installs Aikido Endpoint Protection.app to /Applications with a menu-bar item, and registers the launch agents io.aikido.agent and io.aikido.endpoint.
  6. Approve the macOS permission prompts when they appear: Touch ID for the keychain items the agent creates, Safari browser-extension access, Notifications, and the entries under System Settings → General → Login Items & Extensions.
  7. Restart if it asks. Restart anyway if nothing seems to happen.
Enrollment token The AIK_... token in your install line registers devices to your workspace. Treat it like a password — don't paste the command anywhere.

What it actually does

The endpoint build bundles SafeChain — Aikido's package-install guard — inside the agent. A NetworkExtension Layer 4 proxy intercepts traffic to supported package sources — registries, github.com, browser and IDE extension stores — through a local CA (its root lands in the System keychain, and the installer appends trust env vars — NODE_EXTRA_CA_CERTS, PIP_CERT, CURL_CA_BUNDLE and friends — to your shell rc files plus http.sslCAInfo in git config). Decisions happen on-device: known malware is blocked outright at any age; a too-new version of a clean package is held back — or falls back to an older one — until it passes the minimum-age rule. The "network permission" prompts during setup are the proxy being approved.

Two things it will not stop: a known-malicious package you deliberately approve in the dashboard, and a poisoned release that stays off Aikido's threat feed past the minimum-age window — or slips the automatic exception they grant to scanned-clean versions that fix a critical vulnerability. It reduces typosquat and known-bad risk; it is not a guarantee.

Check it worked

Test the blocking

In Terminal:

npm install aikido-endpoint-test

You should get a block message instead of an install. No npm? The browser check above is enough.

If a package you need gets blocked

Don't turn protection off. From the device's menu in the dashboard, request approval for that package or pause protection on just that device — and turn it back on when you're done.

Uninstall

  1. Delete the device from the dashboard first (Endpoint Protection → Devices → device menu) — reinstalling gets flaky if the old registration is still there.
  2. Run the bundled uninstall script:
    sudo "/Applications/Aikido Endpoint Protection.app/Contents/Resources/scripts/uninstall"
  3. Restart.
Dragging to Trash It isn't enough — the launch agents and filter configuration survive the .app bundle.

Honest limits

Trust tradeoff The local CA makes Aikido a privileged proxy for your registry traffic — the honest cost of intercepting TLS. It uses NetworkExtension, not EndpointSecurity, so it doesn't fight Santa for an ES slot; the two coexist by design.