Yes. Malware is always blocked. No exceptions or policies can override it. Other controls like Force Requests or Block All Installs can be overridden by admins for specific teams or packages. Malware cannot.

Aikido maintains an threat intelligence feed: Aikido Intel. It actively scans new packages using a mix of static rules and AI. Suspicious packages are flagged and our in-house research team investigates from there.

Aikido Endpoint provides broader protection across many ecosystems, while a private registry is best when you need tight control within one specific ecosystem.

It intercepts HTTP traffic at the kernel level, including TLS-encrypted traffic by adding a local CA, and it is designed to work in a chain with other traffic inspection solutions (as the first link).

Aikido Endpoint operates at the package, extension, and AI layer. It complements EDR rather than replacing it. EDR catches threats after they are running. Aikido stops them from running in the first place.

Network blocks are coarse and easy to route around. A developer on a personal hotspot can bypass them entirely. Aikido operates at the workstation level, per developer, per tool. You get granular control and a real audit trail, not a firewall rule that creates the illusion of control.

Minimum package age holds installs of recently published packages. The default is 48 hours. This stops a common supply chain attack. An attacker publishes malicious code to npm or PyPI and tries to get developers to install it before the community can flag it.

NPM, PyPI, Maven, NuGet, VS Code extensions, Open VSX, and Chrome extensions.

Aikido observes traffic at the workstation level regardless of which account a developer is using. If a tool is making outbound calls to an AI service, Aikido sees it. This is true whether it is a corporate license or a personal account.

Windows and Linux support are coming out soon. Availability is likely in Q3 2026