Open-Source Intelligence Platform

MalPkg — Malicious Package Intelligence

Centralized intelligence on malicious, compromised, or suspicious software packages across major ecosystems.

50K+ Packages Analyzed
6 Ecosystems
Real-time Threat Feeds
About

What is MalPkg?

MalPkg is a community-accessible platform that aggregates malicious package indicators, metadata, classifications, and timelines from major software ecosystems. Our mission is to help defenders identify supply-chain risks early and protect their software infrastructure.

Aggregated Data

Consolidated threat intelligence from multiple package repositories and security research.

Timely Updates

Near real-time detection and cataloging of newly discovered malicious packages.

Defensive Focus

Built for security teams to strengthen their supply-chain defenses.

Capabilities

Key Features

Comprehensive tools for supply-chain threat intelligence

Unified Malicious Package Index

Cross-ecosystem correlation and unified view of malicious packages from PyPI, npm, RubyGems, NuGet, and more.

Automated Detection Signals

Behavioral analysis, metadata inspection, and dependency heuristics to identify suspicious patterns.

Threat Intelligence Feeds

Export data in JSON, STIX/TAXII formats with full API integration for automated workflows.

Package Timeline & Diffing

Track version-to-version changes and analyze risk evolution over the package lifecycle.

Search & Filtering

Advanced queries by ecosystem, author, tags, IOCs, risk scores, and more.

Alert Notifications

Configure alerts for new threats matching your dependencies or watch criteria.

Impact

Why It Matters

Supply-chain attacks are among the fastest-growing threats in cybersecurity

Software supply-chain attacks have increased dramatically, with malicious actors targeting package registries to distribute malware at scale. A single compromised dependency can affect thousands of downstream projects and organizations.

MalPkg provides the intelligence needed to stay ahead of these threats, enabling proactive defense rather than reactive incident response.

How Teams Use MalPkg

SOC/IR Workflows

Rapid triage and investigation of package-related alerts

Threat Hunting

Proactive searches for indicators of compromise in your environment

Dependency Auditing

Verify your project dependencies against known malicious packages

CI/CD Security

Integrate checks into your build pipeline to block risky dependencies

Vendor Risk Assessments

Evaluate third-party software for supply-chain risks

Coverage

Data Sources

Comprehensive coverage across major package ecosystems

PyPI
Python
npm
JavaScript
Gems
Ruby
NuGet
.NET
Cargo
Rust
Maven
Java

How We Collect Data

OSINT Sources

Aggregation from public security advisories, CVE databases, and package registry reports.

Automated Analysis

Continuous scanning with behavioral analysis, code inspection, and metadata heuristics.

Community Submissions

Researcher reports and community contributions with verification workflows.

Integration

API Access

Programmatic access to malicious package intelligence

Available Endpoints

GET /api/v1/packages List all cataloged malicious packages
GET /api/v1/packages/{id} Get detailed package information
GET /api/v1/feeds Access threat intelligence feeds (JSON, STIX)
GET /api/v1/search Search packages by various criteria
GET /api/v1/indicators Retrieve IOCs and detection signatures

Example Response

GET /api/v1/packages/mal-example-pkg
{
  "id": "mal-example-pkg",
  "ecosystem": "npm",
  "name": "example-malicious-package",
  "version": "1.0.3",
  "risk_score": 95,
  "classification": "trojan",
  "first_seen": "2024-01-15T08:30:00Z",
  "indicators": {
    "behaviors": ["data_exfiltration", "obfuscation"],
    "network_iocs": ["*.malicious-domain.example"],
    "file_hashes": ["sha256:a1b2c3d4..."]
  },
  "status": "confirmed",
  "references": [
    "https://example.com/advisory/2024-001"
  ]
}
View Full API Documentation
Open Source

Community & Transparency

Built on open collaboration and verified research

Public Submissions

Anyone can submit suspected malicious packages for review. Community contributions help expand coverage and improve detection.

Verified Reports

All submissions undergo verification before publication. We maintain strict quality standards to minimize false positives.

Open Methodology

Our detection criteria and classification methodology are publicly documented. Transparency builds trust.

Researcher Acknowledgments

We credit security researchers who contribute to our database. Recognition for the community that makes this possible.

Want to contribute?

Join our community of security researchers and help protect the software ecosystem.