As title says bot moved following two issues to Drupal core issue queue.
http://drupal.org/node/1534266
http://drupal.org/node/1570358
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | Screen shot 2012-07-12 at 7.08.32 PM.png | 88.95 KB | sheena_d |
As title says bot moved following two issues to Drupal core issue queue.
http://drupal.org/node/1534266
http://drupal.org/node/1570358
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | Screen shot 2012-07-12 at 7.08.32 PM.png | 88.95 KB | sheena_d |
Comments
Comment #1
sheena_d commentedIn the case of #1570358: Comment form not styled completely it was a spam bot that moved the issue. This is not obvious in the issue as of now because the spam comment has been deleted and the reassignment attributed to the last commenter, which happened to be System Message. I received an email notification for the original spam comment that actually moved the issue.
Comment #2
mathankumarc commentedspam bot? how it could be possible?
Comment #3
jthorson commentedThis queue is for the testbots which run Drupal's automated testing infrastructure ... they have no issue moving capabilities, and very limited comment posting abilities at that.
Since it appears that 'System Message' is changing projects and adding tags, moving to the webmaster queue for investigation.
Comment #4
sheena_d commented@mathankumarc - Any commenter can change the project for an issue. When a spammer or spam bot leaves a spam comment, it fills out all fields on the form, and thus can easily change any of the issue settings.
Comment #5
cweagans@sheena_d, this isn't just any commenter though. This is the "System Message" user, which is a utility user on Drupal.org that takes care of test notifications and closing fixed issues after 2 weeks of inactivity.
Bumping this to critical. This is definitely not a good thing.
http://drupal.org/node/1534266#comment-5993080
http://drupal.org/node/1570358#comment-5993074
Comment #6
jthorson commentedJust speculating, but with only two instances and both occuring on the same date and all titles starting with 'Comment'; I wonder if this was the side effect of a one-time bulk node operation gone bad? And if so, who's going to remember what happened a month ago - we aren't likely to ever find the cause.
So it's definately worth investigating; but unless we've seen more than these two occurences, I have trouble seeing it as critical.
Comment #7
jthorson commentedActually, Sheena_D's already explained what happened in comment #1. System Message didn't move the issue; it was just given credit for the move when the actually responsible account (a spambot) was deleted.
... With that said, I'm tempted to mark 'fixed'; pending a second opinion that backs up sheena_d's analysis.
Comment #8
sheena_d commentedTo add a little bit of evidence, I'm attaching a screenshot of the spambot email that changed the ticket settings on #1570358
Not really sure who would be able to back me up on this, I just happened to notice the spam comment when it happened :)
Comment #9
cweagansAh, okay. Well then...
Thanks!