docs(security): warn about malicious "fix" attachment spam#44
Merged
Conversation
Adds an advisory to SECURITY.md covering the automated spam campaign that attaches malware archives (e.g. bd_fix_v1.zip) to issue comments via GitHub's user-attachments uploader. Part of an org-wide response. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a user-facing advisory to
SECURITY.mdabout the active malware-spam campaign: burner accounts reply to fresh issues with an attached*_fix.zip(hosted on GitHub'suser-attachmentsCDN) that claims to be a fix. The note tells users official builds come only from Releases, thatuser-attachments/files/...links are unvetted, and how to report the comment + attachment.Part of the org-wide response (interaction limits + moderation). Docs-only.
🤖 Generated with Claude Code