Spam attack on issue tracker
Asked by asomov:

I recently faced hundreds of spam issues created in my issue tracker.

How can I remove them all ?


Answers:
author: asomov
body: Is there a way to remove the spam tickets ? There are many hundreds of them.


author: mystery_keeper
body: I am having a similar spam attack now.

[https://bitbucket.org/mystery_keeper/vapoursynth-editor/issues?status=new\&status=open](https://bitbucket.org/mystery_keeper/vapoursynth-editor/issues?status=new&status=open)


author: michaelrienstra
body: Here's another one: <https://bitbucket.org/multicoreware/x265_git/issues>

Lots of spam issues created in the time period 2023-03-17 to 2023-03-20, the newest activity is a comment (also spam) created 2023-03-30.

Here's a search that shows many more affected repos: <https://www.google.com/search?q=site%3Abitbucket.org+inurl%3Aissues+%28torrent%7Ccrack%7Cdownload%7Cexe%7Cdownload%29>

The first 23 repos that appeared in that search, sorted alphabetically:  
<https://bitbucket.org/atlassian/agent-smith-wallboard-plugin/issues>  
<https://bitbucket.org/atlassian/atlassian-pocketknife-querydsl/issues>  
<https://bitbucket.org/atlassian/atlassian-util-concurrent/issues>  
<https://bitbucket.org/atlassian/bamboo-cli/issues>  
<https://bitbucket.org/atlassian/cloudtoken/issues>  
<https://bitbucket.org/atlassian/crowd_pam/issues>  
<https://bitbucket.org/atlassian/personal-issue-templates>  
<https://bitbucket.org/atlassian/stash-realtime-editor-plugin/issues>  
<https://bitbucket.org/atlassian/update-all-the-things/issues>  
<https://bitbucket.org/atlassian/vagrant-zscp/issues>  
<https://bitbucket.org/atlassianlabs/ac-gmaps/issues>  
<https://bitbucket.org/atlassianlabs/aiohttp_ac_hipchat/issues>  
<https://bitbucket.org/atlassianlabs/embed-code-plugin/issues>  
<https://bitbucket.org/atlassianlabs/plunk/issues>  
<https://bitbucket.org/atlassianlabs/quickreload/issues>  
<https://bitbucket.org/berkeleylab/upc-specification/issues>  
<https://bitbucket.org/charade/svengine/issues>  
<https://bitbucket.org/gfcstanford/rockstar/issues>  
<https://bitbucket.org/icl/plasma/issues>  
<https://bitbucket.org/MAVERICLab/vcontact2/issues>  
<https://bitbucket.org/multicoreware/hcc/issues>  
<https://bitbucket.org/twocanoes/tcscertrequest/issues>  
<https://bitbucket.org/twocanoes/winclone-beta/issues>

comments: author: michaelrienstra
body: This seems to be the most high-profile (1974 views) discussion of March 2023 issue spam:

<https://community.atlassian.com/t5/Bitbucket-discussions/Dozens-of-spam-issues-being-created-on-bitbucket-osrf-ariac/td-p/2302858>

[@takluyver](/t5/user/viewprofilepage/user-id/3857754) \& [@jestar_jokin](/t5/user/viewprofilepage/user-id/5180178) shared their bulk-delete solutions (Python \& NodeJS) in that discussion.


author: Tom Worster
body: I have been receiving new spam issues as recently as 7 minutes ago.

I made the tracker private.

How can I delete the \~70 spam issues in the last few hours conveniently?

comments: author: Tom Worster
body: I am marking the issues as spam. Should I leave them like that so Atlassian can see them or delete them?


author: Theodora Boudale
body: Hi [@asomov](/t5/user/viewprofilepage/user-id/1847595),

Thank you for reaching out.

I will go ahead and create a support ticket for you using the email of your community account so that we look into this (we won't close this ticket).

Please keep an eye on your inbox for an email with a link to the ticket. After you receive that, please leave a reply to the ticket with the URL of the affected repo(s).

If you have any questions, please feel free to reach out.

Kind regards,  
Theodora

comments: author: asomov
body: The repo:

<https://bitbucket.org/snakeyaml/snakeyaml/>

Its issue tracker:

[https://bitbucket.org/snakeyaml/snakeyaml/issues?status=new\&status=open](https://bitbucket.org/snakeyaml/snakeyaml/issues?status=new&status=open)


author: Theodora Boudale
body: Thank you [@asomov](/t5/user/viewprofilepage/user-id/1847595), I see that you posted it in the support ticket as well. We will provide further updates via the support ticket.

Kind regards,  
Theodora


author: mystery_keeper
body: [@Theodora Boudale](/t5/user/viewprofilepage/user-id/818086)

It's not an individual issue. You need to stop the ongoing mass spam attack.

And user instruments for dealing with multiple tickets would be nice too.


author: Tom Worster
body: Correct. Not individual. I am also seeing these.

Can I see the progress in the support ticket [@Theodora Boudale](/t5/user/viewprofilepage/user-id/818086) mentioned?

Atlassian should treat this as an attack on their system.


author: Theodora Boudale
body: Hi [@mystery_keeper](/t5/user/viewprofilepage/user-id/5172759) and [@Tom Worster](/t5/user/viewprofilepage/user-id/3039181),

We are aware that multiple workspaces/repos are targeted and our engineering team is working to address the issue.

I will create a separate support ticket for each of you in the next few minutes. You should receive an email with a link to the support ticket. You can provide there the URL of the affected issue tracker and ask any questions you have.

In the meantime, we recommend temporarily making the issue tracker private.

Kind regards,  
Theodora


author: mbgvhh
body: Ok, here's another one: [https://bitbucket.org/geowerkstatt-hamburg/masterportal/issues?status=new\&status=open\&page=5\&sort=-id](https://bitbucket.org/geowerkstatt-hamburg/masterportal/issues?status=new&status=open&page=5&sort=-id)

Please delete Issues #895-#1015 .


author: asomov
body: [@Theodora Boudale](/t5/user/viewprofilepage/user-id/818086)my issue tracker stays closed very long.

1. Can hundreds of issues be removed (I do not want to pollute the issue tracker)

2. Can I open the issue tracker ?


author: Fabio Racobaldo _Herzum_
body: Hi [@asomov](/t5/user/viewprofilepage/user-id/1847595) ,

please raise an issue through <https://support.atlassian.com/contact/>

In the past there was a similar issue (<https://jira.atlassian.com/browse/BCLOUD-4179>)

Fabio

comments: author: asomov
body: Hi Fabio. I did but I was forwarded here (by Sheng).

It looks like there is no solution. I have to either manually remove all the spam tickets (they have tripled the amount) or stop using the issue tracker.

Andrey


Tags: bitbucket-cloud

cloud