By https://www.facebook.com/swapankmanna/
Publication Date: 2026-05-26 14:49:00
Perplexity Bumblebee: SBOMs scan repositories. EDR products watch running processes. Neither looks at the raw, on-disk state of a developer’s local environment, with lockfiles, extension manifests, and AI tool configs scattered across a home directory.
That gap became very visible on May 11, when a group Google tracks as UNC6780 slipped malicious code into packages used by TanStack, SAP, and Zapier, among others. One affected package had 12 million weekly downloads. The attack spread the moment developers ran npm install, because npm packages can carry postinstall scripts that execute automatically on install. Any scanner that invokes npm to check for exposure runs those same scripts. You go looking for the worm; the worm runs.
Bumblebee avoids this entirely. It just reads package-lock.json, go.sum, *.dist-info/METADATA, and equivalent files directly.
Perplexity Bumblebee Deep-Dive: Verifying Zero-Execution Claims Against Real-World Attack Surfaces
| Perplexity’s Claim | What It Means in Practice |
| Read-only scanner, no code execution | Scans cannot trigger malicious postinstall attacks. |
| Covers MCP configs | The first open-source tool to secure AI connector files. |
| Three scan profiles | Profiles fit different use cases, but teams must handle scheduling. |
| Ships with threat catalog | Catalog quality relies on ongoing, manual human review. |
| Zero non-stdlib dependencies | Highly secure scanner base, but requires Go 1.25. |
