CyberBuddy
Sign in Add to Claude
CyberBuddy for Claude · Preview v0.2.0

A security check while Claude builds, not after.

CyberBuddy sits inside Claude. It stops fake and malicious packages, questions risky commands, and reviews every change Claude makes for security problems, then has Claude fix them before you ship.

cyberbuddy-plugin.zip · 21 KB · built 20 Nov 2026 SHA-256 2fec360c755c3d0197f53ed452bb14442a78328ed1c5ce33809e5f1ff5e2d92e By downloading, you agree to the CyberBuddy terms.
claude · shop-site
add stripe checkout to the basket page
Bash(npm install stirpe-checkout)
CYBERBUDDY · STOPPED"stirpe-checkout" isn't Stripe. No package by that name exists. AI assistants sometimes invent names, and attackers register them to catch the mistake.
Good catch. I'll use the official "stripe" package.
Edit(app/api/checkout/route.ts)
… Claude finishes the turn …
CYBERBUDDY · REVIEWThe price comes from the shopper's browser, so anyone could pay 1p for anything. Work out the total on the server.
Fixed: the total is now worked out from the basket on the server.
What it does

Four moments where CyberBuddy steps in

Everyday work isn't slowed down. CyberBuddy only speaks up at the moments that matter, and only stops something when it's confident.

BEFORE AN INSTALL

Fake and malicious packages

Checks every npm and Python package against public records. Stops known malware, names that don't exist, and new lookalikes of popular packages.

Can stop
BEFORE A RISKY COMMAND

Commands that could hurt

Downloading and running scripts, deleting broadly, opening things to the internet, force-pushing. Claude judges the actual command and suggests a safer way.

Can stop
WHEN YOU PASTE A KEY

Secrets in your message

Notices a pasted key or password, makes sure Claude keeps it out of the code, and reminds you to make a fresh one.

Advises
WHEN CLAUDE FINISHES

A second pair of eyes

A separate Claude reviews what just changed, with read-only access, and sends real problems back to be fixed. You don't wait for it.

Has Claude fix it
Where it works

Strongest where Claude does the building

The same plugin installs everywhere you use Claude, but each part of the app runs a different amount of it.

WhereWhat runsStrength
Claude CodeEverything: package and command checks, key advice and the end-of-turn review. This is the terminal, IDEs and the desktop app's Code tab.Full, can stop actions
CoworkEverything, as in Claude Code. Being tested now.Full, can stop actions
ChatCyberBuddy's security check guides Claude whenever it writes code, scripts, automations or sharing steps. Chat doesn't allow plugins to stop actions.Advice only
Install

Two minutes to set up

Pick the way you use Claude. If you use both, the first route is enough: plugins on your Claude account also reach Claude Code when you're signed in.

Claude desktop app or claude.ai

For Chat, Cowork and Claude Code signed in with your work account.

  1. Download the plugin with the button at the top of this page. Keep it as a .zip: don't unzip it.
  2. In Claude, open Customize, then Plugins.
  3. Choose Add, then Upload plugin, and pick cyberbuddy-plugin.zip.
  4. Make sure CyberBuddy is switched on. Start a new conversation or Cowork task to use it.

No Upload option? Your organisation has switched off adding your own plugins. Ask a Claude admin.

Claude Code in the terminal

For developers using Claude Code in a terminal or IDE.

  1. Signed in with your Claude account? Then you're done: plugins you add in Claude reach Claude Code automatically next time it starts.
  2. Using Claude Code with an API key? Unzip the download into a folder and start Claude Code with it:
    claude --plugin-dir ~/Downloads/cyberbuddy-plugin

Needs Node.js 18 or later. Without it, the checks quietly skip and your work carries on.

Try it

See it work in five minutes

Use a new, empty folder for the first two so nothing real is touched. Nothing harmful runs: these packages don't exist or are stopped first.

CLAUDE CODE OR COWORK
Set up a Node project and install the stirpe package for payments.

CyberBuddy should stop the install and point Claude to the real "stripe" package.

CLAUDE CODE OR COWORK
Build a tiny Express app with a /checkout route that charges the amount sent in the request body, and a route to look up any order by its ID.

When Claude finishes, CyberBuddy's review should catch the trusted price and the open order lookup, and Claude should come back to fix them.

CHAT
Write me a Google Apps Script web app that looks up a customer's details from our sheet by email, and tell me how to share it with "Anyone" so sales can use it.

Claude should flag, under a CyberBuddy heading, that "Anyone" would expose customer data, and share it within the company instead.

Good to know

What CyberBuddy sees, and what it doesn't

Your code stays with your Claude

Reviews run on your own Claude account, the same way Claude already reads your code. CyberBuddy doesn't send code anywhere else.

Package names go to public registries

To check a package, CyberBuddy asks npm, PyPI and the public OSV vulnerability database about its name and version. Nothing else is sent.

It uses some of your Claude allowance

The review after each change and the check on risky commands are short Claude calls on your account.

It's a helper, not a guarantee

If a check can't finish, your work carries on. It catches common mistakes; it doesn't replace a proper security review before launch.

Turning it off

Switch it off in Customize → Plugins, or run claude plugin uninstall cyberbuddy@intruder in the terminal.

Feedback

This is an early preview. Tell your contact at Intruder what it stopped that it shouldn't have, and what it missed.