Attackers don't target your code. They target what you install: packages, MCP servers, IDE and agent extensions. SafeDep blocks malicious packages at every entry point, before they run.
No credit cardFree forever for individual useStart with GitHub
SafeDep analyzes every package published to the major registries, around the clock. Our research team publishes the breakdown, often before the ecosystem has an advisory.
npmMini Shai-Hulud Strikes Again: 317 npm Packages CompromisedOne compromised maintainer account published 637 malicious versions.317 packages
PyPIMalicious litellm 1.82.8: Credential Theft and Persistent BackdoorA .pth file triggers credential theft the moment the package installs.AWS + K8s secretsnpmShai-Hulud 2.0 npm Supply Chain Attack Technical AnalysisSelf-replicating malware in zapier-sdk, @asyncapi, posthog and @postman.25,000+ reposThird-party code arrives at every hand-off in your pipeline, from a developer's terminal to an org-wide registry. Each arrival is an execution, and none of it was reviewed by anyone on your team.
Five entry points. One unchecked component is enough.
One policy, enforced everywhere the component travels, so it is inspected before it runs, merges, builds or spreads across the org.
Credential theft, reverse shells, data exfiltration. These are purpose-built attacks, not bugs a vulnerability scanner can match against a database. Every screen below is the real product.
SafeDep sits in front of npm, pnpm, pip, uv, bun and other package managers and blocks malicious packages at install time, before any post-install script runs. Every decision lands in one fleet view, alongside a live feed of what was just blocked and where.
SafeDep MCP checks each package an agent wants before it installs. The advisory trail shows which agent asked for what, so a malicious pull is attributed rather than anonymous.
vet inventories what each machine actually has loaded: coding agents, MCP servers and CLI tools, with scope and version. None of it appears in a lockfile, so none of it shows up in a repo scan.
The GitHub App posts a summary on each pull request: malware, vulnerability and license checks, with a verdict per package. It runs as a required check, so nothing reaches main unreviewed.
SafeDep runs as a proxy in the pipeline and intercepts every package install. A malicious package is stopped before it reaches the runner, and the job exits non-zero on the policy violation.
Every enforcement point is open source and auditable, so there is nothing to take on trust. SafeDep Cloud is what turns those same tools into protection for a whole organization.
The command-line tools that do the actual blocking. Free forever, and yours to read.
brew install safedep/tap/pmg
Everything in the open source tools, plus the org-wide layer: which components exist, who pulled them in, what policy blocked what, and proof for the audit.
Security
The October 29, 2026 Binance hack started on developer laptops. A tampered Homebrew install and a fake job interview gave a North Korean group its first access. A short breakdown of the attack path.
Malware
A forged commit force-pushed to the antd-img-crop GitHub repository runs a dropper on npm run build that installs a cross-platform stealer and remote-access agent called OverLord. The npm package is clean.
Security
October was Cybersecurity Awareness Month. It was also the month PHP, Railway, OpenCode, Binance, Polymarket, Cursor, LiteLLM and eight more made the news for a security incident. A short recap of what happened to each one.
Start free with open source tools on your machine. Scale to a unified platform for your organization.
