Spam attack on issue tracker

[asomov]

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

How can I remove them all ?

[asomov]

Is there a way to remove the spam tickets ? There are many hundreds of them.

[mystery_keeper]

I am having a similar spam attack now.

https://bitbucket.org/mystery_keeper/vapoursynth-editor/issues?status=new&status=open

[michaelrienstra]

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

[michaelrienstra]

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 & @jestar_jokin shared their bulk-delete solutions (Python & NodeJS) in that discussion.

[Tom Worster]

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?

[Tom Worster]

I am marking the issues as spam. Should I leave them like that so Atlassian can see them or delete them?

[Theodora Boudale]

Hi @asomov,

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

[asomov]

The repo:

https://bitbucket.org/snakeyaml/snakeyaml/

Its issue tracker:

https://bitbucket.org/snakeyaml/snakeyaml/issues?status=new&status=open

[Theodora Boudale]

Thank you @asomov, I see that you posted it in the support ticket as well. We will provide further updates via the support ticket.

Kind regards,
Theodora

[mystery_keeper]

@Theodora Boudale 

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.

[Tom Worster]

Correct. Not individual. I am also seeing these.

Can I see the progress in the support ticket @Theodora Boudale mentioned?

Atlassian should treat this as an attack on their system.

[Theodora Boudale]

Hi @mystery_keeper and @Tom Worster,

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

[mbgvhh]

Ok, here's another one: https://bitbucket.org/geowerkstatt-hamburg/masterportal/issues?status=new&status=open&page=5&sort=-id

Please delete Issues #895-#1015 .

[asomov]

@Theodora Boudalemy 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 ?

[Fabio Racobaldo _Herzum_]

Hi @asomov ,

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

[asomov]

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