Your Dev Machine's Hidden Threat

Developer machines represent a critical, often overlooked, vulnerability in the modern software supply chain. Traditional security practices heavily emphasize scanning source repositories, build containers, and production environments. This approach entirely misses the messy local state of developer laptops, which harbor old project clones, globally installed packages across ecosystems like npm, PyPI, and Go modules, alongside ephemeral test environments, editor extensions, and browser add-ons.

A single compromised developer machine can become the initial entry point for a widespread supply chain attack, effectively bypassing robust production safeguards. During an incident, the critical question shifts from "Is production safe?" to "Did any developer install this risky package, extension, or AI config locally?". This glaring gap leaves organizations blind to potential threats residing on individual endpoints, facilitating lateral movement and broader compromise.

Adding to this complexity, the rapid adoption of AI coding tools introduces a new, unmonitored attack surface. Local agents and Model Context Protocol (MCP) configs now reside on developer machines, often containing sensitive data, much like environment variables. These configurations become prime targets, creating vectors that traditional scanners are ill-equipped to detect or monitor. Identifying these granular components requires a read-only inventory tool that avoids executing potentially malicious code, providing crucial visibility into an expanding threat landscape.

Perplexity's open-source Bumblebee scanner addresses the messy reality of developer machines with a fundamentally read-only strategy. It safely inventories potential threats by directly parsing static metadata files—like `package-lock.json`, `yarn.lock`, `go.mod`, and extension manifests—from the disk. This approach provides a comprehensive, non-intrusive snapshot of installed packages, editor extensions, and AI configurations without altering the local environment.

A core design tenet prohibits Bumblebee from ever executing package managers like `npm ls`, `pip show`, or `go list`, nor does it run any project code. This critical safeguard prevents the accidental activation of malicious post-install scripts, a significant risk when scanning for compromised dependencies during an incident. The tool’s passive inspection ensures system integrity, making it safe for even the most sensitive environments.

Bumblebee outputs its findings as clean, structured NDJSON records, detailing ecosystem, package name, version, and source file. This highly scriptable format allows organizations to integrate results directly into their existing security workflows. Teams can pipe output into SIEMs, MDM systems, or custom scripts, facilitating rapid, fleet-wide analysis and incident response across all developer endpoints.

Bumblebee carves out a distinct niche, operating beyond the scope of traditional security tools. It is not an SCA (Software Composition Analysis) tool, which focuses on application dependencies, nor an SBOM (Software Bill of Materials) tool, which inventories shipped artifacts. Unlike EDR (Endpoint Detection and Response) systems that monitor running code, Bumblebee inventories the local developer state, a critical blind spot for many organizations.

Its coverage is exceptionally broad, scanning far more than just application packages. Bumblebee inspects global and user-level package managers like npm, PyPI, Go modules, and RubyGems. It also inventories editor extensions (e.g., VS Code), browser extensions, and emerging AI tool configurations like Model Context Protocol (MCP) JSON files, all prevalent on a modern developer machine.

Flexible scan profiles empower teams to adapt to various security needs. A 'Baseline' profile offers routine inventory of common global and user-level components. The 'Project' profile targets specific workspace directories, focusing on lock files within active development folders. For incident response, the 'Deep' profile allows targeted hunts across explicit roots, like a known compromised package. Perplexity Is Open-Sourcing Bumblebee details Perplexity's internal development and subsequent decision to open-source this tool, emphasizing its read-only metadata parsing approach for safe, fast insights.

Establish a robust security posture with a simple, powerful workflow. Implement Bumblebee's baseline scan weekly across all developer machines. This continuously updates a comprehensive inventory of local developer state, including global packages, user-level toolchains, editor extensions, browser extensions, and supported Model Context Protocol (MCP) configurations. This proactive approach ensures a current, fleet-wide understanding of potential vulnerabilities.

During a security incident, this meticulously maintained inventory provides immediate, verifiable answers. Traditional incident response often involves asking developers to manually execute package manager commands like `npm ls` or `pip show`, a risky action that could inadvertently trigger malicious code. Bumblebee's read-only approach circumvents this danger, allowing security teams to instantly query historical snapshots and identify exposed machines without further risk.

Bumblebee delivers crucial visibility within the first hour of a crisis, transforming chaotic searches into data-backed certainty. It answers the critical question, "Did anyone install this thing locally?" with verifiable data, not panicked Slack messages or manual checks. This rapid, precise insight into developer endpoint inventory is indispensable for initiating a swift and effective incident response, securing systems before threats escalate.

What is Perplexity Bumblebee?

Bumblebee is an open-source, read-only scanner from Perplexity that inventories packages, extensions, and AI tool configurations on developer machines by parsing local metadata without executing code.

How is Bumblebee different from SCA or EDR tools?

SCA tools scan application dependencies, and EDR tools monitor running processes. Bumblebee focuses on the 'at-rest' state, inventorying all developer-related files on disk to identify potential threats before they are executed or shipped.

Is Bumblebee safe to run during a security incident?

Yes, its read-only design is its key safety feature. By not running package managers or executing project code, it avoids accidentally triggering malicious scripts that might be present in a compromised package.

What systems does Bumblebee support?

Bumblebee is a single Go binary that currently runs on macOS and Linux. It scans a wide range of ecosystems, including npm, pnpm, Yarn, Bun, PyPI, Go modules, VS Code extensions, and browser extensions.