Perplexity open-sources Bumblebee to lock down dev machines
Perplexity just open-sourced Bumblebee, its internal security scanner built to protect developer machines against supply-chain attacks. Built with Go for macOS and Linux, it checks local packages, editor extensions, and MCP configs entirely in read-only mode—meaning it never runs install scripts or triggers the very malware it hunts for.

Bumblebee is an open-source security scanner from Perplexity designed to protect local developer machines from supply-chain threats.
It is the exact tool Perplexity uses internally to secure the developer environments powering its core services, Comet, and Computer. When a fresh supply-chain exploit hits the news, security teams can run it to immediately check which endpoints are exposed.
What it actually inspects
Most open-source security checkers only look at one or two surfaces. Bumblebee scans across four major local vectors at once.
First, it covers language package managers, supporting npm, pnpm, Yarn, Bun, PyPI, Go modules, RubyGems, and Composer.
Second, it audits AI agent configurations, specifically checking MCP setups.
Third, it tracks editor extensions across the VS Code ecosystem, covering VS Code, Cursor, Windsurf, and VSCodium.
Fourth, it scans browser extensions across Chromium variants like Chrome, Comet, Edge, Brave, and Arc, as well as Firefox.
Bumblebee ships with three scan profiles. Baseline handles routine periodic sweeps through fleet management or MDM. Project targets specific workspaces or repositories. Deep is built for urgent incident-response sweeps. Every flagged finding links directly back to the specific threat catalog entry, timestamp, and source evidence.
A strict read-only design that never runs code
The cleverest part of Bumblebee is how it handles file evaluation.
Modern package-manager attacks frequently hide inside postinstall scripts, which detonate automatically the moment npm install touches a folder. A scanner that calls out to npm to query package versions can trigger the very malware payload it is hunting for.
Bumblebee completely eliminates that risk by remaining strictly read-only. It never runs lifecycle hooks or postinstall scripts. It never invokes tools like npm, pnpm, bun, or pip. It does not even read your application source code, sticking purely to lockfiles, manifests, and installed metadata.
It is also worth noting that Bumblebee is not an EDR. It does not monitor active runtime processes or network traffic, keeping its scope focused purely on metadata-level exposure.
Getting started
Bumblebee is available as an open-source Go project targeting macOS and Linux developer machines.
Security and platform teams can clone the repository, point it at their own curated catalog of malicious or vulnerable versions, and pipe the output into existing alert pipelines.
Why it matters
We think Bumblebee hits a critical sweet spot in modern engineering security. Developer endpoints are increasingly loaded with specialized AI agent setups, local MCP servers, and custom editor forks, all of which fall outside the sightlines of traditional CI scanners and enterprise antivirus tools.
If your engineering organization relies heavily on tools like Cursor, Windsurf, or MCP-connected workflows, this is an easy tool to adopt. It provides fast visibility into high-risk local environments without introducing the dangerous execution side effects that plague ordinary CLI scanners.
Sources (1)
- perplexity.ai(opens in a new tab)Originalperplexity.ai