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.
2fec360c755c3d0197f53ed452bb14442a78328ed1c5ce33809e5f1ff5e2d92e
By downloading, you agree to the CyberBuddy terms. Everyday work isn't slowed down. CyberBuddy only speaks up at the moments that matter, and only stops something when it's confident.
Checks every npm and Python package against public records. Stops known malware, names that don't exist, and new lookalikes of popular packages.
Can stopDownloading and running scripts, deleting broadly, opening things to the internet, force-pushing. Claude judges the actual command and suggests a safer way.
Can stopNotices a pasted key or password, makes sure Claude keeps it out of the code, and reminds you to make a fresh one.
AdvisesA 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 itThe same plugin installs everywhere you use Claude, but each part of the app runs a different amount of it.
| Where | What runs | Strength |
|---|---|---|
| Claude Code | Everything: 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 |
| Cowork | Everything, as in Claude Code. Being tested now. | Full, can stop actions |
| Chat | CyberBuddy's security check guides Claude whenever it writes code, scripts, automations or sharing steps. Chat doesn't allow plugins to stop actions. | Advice only |
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.
For Chat, Cowork and Claude Code signed in with your work account.
No Upload option? Your organisation has switched off adding your own plugins. Ask a Claude admin.
For developers using Claude Code in a terminal or IDE.
claude --plugin-dir ~/Downloads/cyberbuddy-pluginNeeds Node.js 18 or later. Without it, the checks quietly skip and your work carries on.
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.
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.
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.
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.
Reviews run on your own Claude account, the same way Claude already reads your code. CyberBuddy doesn't send code anywhere else.
To check a package, CyberBuddy asks npm, PyPI and the public OSV vulnerability database about its name and version. Nothing else is sent.
The review after each change and the check on risky commands are short Claude calls on your account.
If a check can't finish, your work carries on. It catches common mistakes; it doesn't replace a proper security review before launch.
Switch it off in Customize → Plugins, or run claude plugin uninstall cyberbuddy@intruder in the terminal.
This is an early preview. Tell your contact at Intruder what it stopped that it shouldn't have, and what it missed.