Skip to content

Commit c774aa2

Browse files
authored
Merge pull request #94 from l3montree-dev/add-reference-malicious-packages
Added malicious packages reference page
2 parents ed474d0 + 12a0a2b commit c774aa2

1 file changed

Lines changed: 19 additions & 2 deletions

File tree

src/pages/reference/vulnerability-database/malicious-packages.mdx

Lines changed: 19 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,23 @@ import {
77
} from '@/components/ui/tooltip'
88
import PageContentComingSoon from '@/components/PageContentComingSoon'
99

10-
# Malicious Packages
10+
# OSSF Malicious Packages
1111

12-
<PageContentComingSoon />
12+
The OSSF Malicious Packages repository is an open-source database containing reports of malicious packages identified across different open-source package repositories.
13+
14+
## Scope
15+
Instead of listing unintentional weaknesses like CVEs, malicious packages focus more on intentional malicious patterns like typosquatting attacks, account takeovers, dependency confusion, or manifest confusion, just to name a few.
16+
17+
18+
The OSSF explicitly defines malicious packages as those that, when installed or used, compromise system confidentiality, availability, and/or integrity.
19+
20+
## Data Access
21+
22+
Malicious packages can be accessed via the public [GitHub repository](https://github.com/ossf/malicious-packages), located in the osv directory.
23+
Additionally, the OSSF publishes [up-to-date statistics](https://ossf.github.io/malicious-packages/stats/) on total malicious packages.
24+
25+
## Malicious Packages in DevGuard
26+
27+
DevGuard will be using Malicious Packages in the upcoming purl inspector:
28+
29+
<PageContentComingSoon/>

0 commit comments

Comments
 (0)