Most security tools catch bad packages after they've already landed in your project. Replit's new Package Firewall flips that model entirely -- it intercepts malicious installs at the network level, before any code ever reaches your environment. Launched in partnership with supply-chain security firm Socket, the feature is already blocking around 8,000 malicious package installs per day across the platform.

The window nobody was watching

The standard playbook for dependency security goes something like this: scan your project before you publish, check your lock file, run npm audit. The problem is that all of those checks happen after installation. Replit already scans projects for vulnerable dependencies and audits dependencies before publishing -- but risk shows up earlier than that, the moment a malicious package gets installed.

Socket intercepts packages before they install, catching novel malware through behavioral analysis, while traditional tools like Snyk monitor installed dependencies after publish, alerting on newly-disclosed CVEs. That gap matters enormously for a specific class of threat: malware that does its damage the instant it runs -- stealing secrets, opening backdoors, or exfiltrating environment variables. By the time a publish-time scan flags it, the attack has already succeeded.

How it works

When you or the Replit Agent run an install command like npm install or pip install, the request passes through Package Firewall. If the package is clean, the install runs as usual. If Socket has flagged the package as malicious or compromised, the install is blocked before any code reaches your environment.

When something gets blocked, you get a clear message explaining what was stopped and why, with a link to Socket's findings for that package. Crucially, the Replit Agent sees the same signal -- so it can suggest a safe alternative or hand the decision back to you rather than silently failing or retrying with a different (potentially worse) package.