Skip to main content
A malicious package is an open-source package built or altered to harm whoever installs it: stealing secrets, opening a backdoor, or running unwanted code. Unlike a vulnerability, which is an unintended flaw in an otherwise legitimate package, a malicious package is harmful by design.

​
Common forms

  • Typosquatting and dependency confusion: a package named to be mistaken for a popular or internal one.
  • Malicious install scripts: code that runs the moment a package is installed, before you ever import it.
  • Backdoors and data exfiltration: harmful behavior hidden inside otherwise working code.
  • Compromised releases: malicious code injected into a previously trusted package, usually in a fresh version.

​
How SafeDep detects them

SafeDep monitors public package registries (npm, PyPI, RubyGems, and more) and analyzes new and updated packages with:
  • Static analysis of the package’s code,
  • Dynamic analysis of its runtime behavior (network, file system, and process activity),
  • Metadata analysis of the package and its publisher.
Suspicious packages are verified by security experts before classification. The result feeds a real-time malicious package database that every SafeDep tool reads from.

​
Blocking malicious packages

Detection is how SafeDep knows a package is malicious. Blocking it is the job of Package Security:
  • PMG blocks them at install time on developer machines.
  • Vet blocks them in CI/CD.
  • The SafeDep MCP server lets AI coding agents check a package before suggesting it.

Vulnerability

The other kind of dependency risk: unintended flaws in legitimate packages.

Package Security

Block malicious packages at every entry point.

Malware Analysis

Analyze a package on demand in SafeDep Cloud.

Policy

Turn detection into enforceable rules.