Malware Detection in Open-Source Dependencies and Containers

Malware Detection in Open-Source Dependencies

When you connect your code repositories to Aikido, it will scan all installed packages for malware, such as obfuscated code, code that unexpectedly exfiltrates data to an unknown server, code that attempts to execute commands during installation on the developer's machine or installs bitcoin miners.

This functionality is automatically enabled on the All Plans. Aikido discovers up to 1000 malicious packages in the ecosystems per day. To view the latest statistics, click here.

15 Ecosystems Supported

• NPM

• PyPI

• GitHub Actions

• Packagist

• Ruby

• VS Code

• Open VSX

• NuGet

• Maven

• Chrome

• Rust

• Go

• WordPress

• Skills

• Drupal

Check Whether You Are Exposed

You can check whether malicious packages affect your environment in the Malware Monitor under Reports → Malware Monitor.

Malware Detection in Containers

As an extra measure, we also scan for malware in your containers. This is important as there is not always a code-related Lockfile that would flag the malware or when your organization pulls from public or private registries before they ever reach production.

Container malware scanning is automatically enabled on the Pro plan and runs continuously as new container images are introduced into your environment.

Prevent Malware During Installation with Safe Chain

If you want to stop malicious packages before they are ever installed on the developer's workstation, use Safe Chain.

Safe Chain adds protection directly to your package installs. It checks packages and nested dependencies during install and blocks known malicious behavior such as obfuscated code, data exfiltration, install scripts, and crypto miners.

This complements malware detection in repositories and containers. It helps you catch threats earlier in the developer workflow, before they reach your codebase, CI, or production systems.