mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1706] Rickroll attack #1188
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#1188
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tripleee on GitHub (Apr 16, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1706
Describe the bug
Some lowlife spammed all my monitoring feeds, and presumably everyone else's too, with a Youtube link last night.
Components impacted
In so many words, this impacted basically every component of the system.
Screenshots and/or logs
I can provide a screenshot of my phone's home screen this morning, but I guess you can imagine it even without the evidence.
Additional context
I suppose the "bug" here is that they were able to enumerate all monitoring endpoints. At a minimum, there should perhaps be a way to opt out of having them visible to everyone.
@binwiederhier commented on GitHub (Apr 16, 2026):
Somebody reported this last night. I confirmed that somebody is crawling GitHub for ntfy topics and publishing to them. I confirmed that all topics that were published to I could find through GitHub search.
I posted this last night on discord
I deployed a banning mechanism:
github.com/binwiederhier/ntfy-ansible@b3f0407260But basically: keep your topics private, otherwise people will be able to publish to it.
@tripleee commented on GitHub (Apr 18, 2026):
Thanks for the analysis and the fix! I suppose it might make sense to leave this bug report open for a while for visibility. I checked your blog etc and found no mention before posting here.