HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bf
security-advisories
Security & Privacy2025–2025
bf / security-advisories

security-advisories

Security advisories for vulnerabilities

4Distinct people
5Mentions
0Explicit recommenders
68GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Security advisories for vulnerabilities

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval5 dated mentions

Observed mentions: 2025-01-16 15:46:46 UTC to 2025-01-18 05:57:05 UTC.

0122025-01-16 15:00:00 UTC to 2025-01-16 18:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsJan 16, 15:002025-01-16 18:00:00 UTC to 2025-01-16 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-16 21:00:00 UTC to 2025-01-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-17 00:00:00 UTC to 2025-01-17 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-17 03:00:00 UTC to 2025-01-17 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-17 06:00:00 UTC to 2025-01-17 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-17 09:00:00 UTC to 2025-01-17 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 17, 09:002025-01-17 12:00:00 UTC to 2025-01-17 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-17 15:00:00 UTC to 2025-01-17 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-17 18:00:00 UTC to 2025-01-17 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-17 21:00:00 UTC to 2025-01-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-18 00:00:00 UTC to 2025-01-18 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-18 03:00:00 UTC to 2025-01-18 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 18, 03:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 16, 15:002025-01-16 15:00:00 UTC2025-01-16 18:00:00 UTC211
Jan 16, 18:002025-01-16 18:00:00 UTC2025-01-16 21:00:00 UTC000
Jan 16, 21:002025-01-16 21:00:00 UTC2025-01-17 00:00:00 UTC101
Jan 17, 00:002025-01-17 00:00:00 UTC2025-01-17 03:00:00 UTC000
Jan 17, 03:002025-01-17 03:00:00 UTC2025-01-17 06:00:00 UTC000
Jan 17, 06:002025-01-17 06:00:00 UTC2025-01-17 09:00:00 UTC000
Jan 17, 09:002025-01-17 09:00:00 UTC2025-01-17 12:00:00 UTC000
Jan 17, 12:002025-01-17 12:00:00 UTC2025-01-17 15:00:00 UTC101
Jan 17, 15:002025-01-17 15:00:00 UTC2025-01-17 18:00:00 UTC000
Jan 17, 18:002025-01-17 18:00:00 UTC2025-01-17 21:00:00 UTC000
Jan 17, 21:002025-01-17 21:00:00 UTC2025-01-18 00:00:00 UTC000
Jan 18, 00:002025-01-18 00:00:00 UTC2025-01-18 03:00:00 UTC000
Jan 18, 03:002025-01-18 03:00:00 UTC2025-01-18 06:00:00 UTC101

What Hacker News says

2 sources
Haha, this would be an amazing way to test the ChatGPT crawler reflective DDOS vulnerability [1] I published last week. Basically a single HTTP Request to ChatGPT API can trigger 5000 HTTP requests by ChatGPT crawler to a website. The vulnerability is/was thoroughly ignored by OpenAI/Microsoft/BugCrowd but I really wonder what would happen when ChatGPT crawler interacts with this tarpit several times per second. As ChatGPT crawler is using various Azure IP ranges I actually think the tarpit would crash first. The vulnerability reporting experience with OpenAI / BugCrowd was really horrific. It's always difficult to get attention for DOS/DDOS vulnerabilities and companies always act like they are not a problem. But if their system goes dark and the CEO calls then suddenly they accept it as a security vulnerability. I spent a week trying to
Read the rest
reach OpenAI/Microsoft to get this fixed, but I gave up and just published the writeup. I don't recommend you to exploit this vulnerability due to legal reasons. [1] https://github.com/bf/security-advisories/blob/main/2025-01-...
In Nepenthes is a tarpit to catch AI web crawlers

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.