Wikipedia:Administrator intervention against vandalism

Report active, obvious, and persistent vandals and spammers here.

Before reporting, read the spam and vandalism pages, as well as the AIV guide. To submit, edit this page and follow the instructions at the top of the "User-reported" section. For other issues, file a request for administrator attention. Important! The edits of the user must be obvious vandalism or obvious spam. Except for egregious cases, the user must have been given enough warning(s). The warning(s) must have been given recently and there must be reasonable grounds to believe the user(s) will further disrupt the site in the immediate future. If you decide that a report should be filed place the following template at the bottom of the User-reported section: * {{Vandal|Example user or IP}} Your concise reason (e.g. vandalised past 4th warning). ~~~~ Requests for further sanctions against a blocked user (e.g., talk page, e-mail blocks) should be made at Wikipedia:Administrators' noticeboard/Incidents. Reports of sockpuppetry should be made at Wikipedia:Sockpuppet investigations unless the connection between the accounts is obvious and disruption is recent and ongoing. This noticeboard can grow and become backlogged. Stale reports are automatically cleared by MDanielsBot after 4–8 hours with no action. You can subscribe to a web feed of this page in either RSS or Atom format.

This page was last updated at 03:30 on 20 November 2024 (UTC). if it is out of date.

Reports

Bot-reported

• 27.125.164.22 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) – Tripped filter 3 five times in the last 5 minutes (New user blanking articles, details). Report false positive. DatBot (talk) 02:34, 20 November 2024 (UTC)

User-reported

• 2A02:A213:2281:DA80:0:0:0:179 (talk · contribs · (/64) · deleted contribs · filter log · WHOIS · RBLs · http · block user · block log) – On See contribs (contribs&oldid= diff): account is evidently a spambot or a compromised account. E_F⁵ 23:55, 19 November 2024 (UTC)

  No vandalism since final warning. Re-report if this user resumes vandalising. ThadeusOfNazereth(he/him)^{Talk to Me!} 00:11, 20 November 2024 (UTC)

  (Non-administrator comment) @ThadeusOfNazereth: This IP has shown the same pattern of disruption going back years. TornadoLGS (talk) 01:22, 20 November 2024 (UTC)

  Years? There's nithing on the /64 more than a couple of months old and while I'd agree it looks like the same person, they haven't been warned until today. Unless the edits are grotesque there's not much to lose from giving them one more chance. HJ Mitchell | Penny for your thoughts? 01:29, 20 November 2024 (UTC)

  (Non-administrator comment)@HJ Mitchell: OK not the exact same it seems. Still a similar IP range and the behavior pattern matches this LTA: 2A02:A213:2A81:8500:0:0:0:1EE (talk · contribs · WHOIS) TornadoLGS (talk) 01:37, 20 November 2024 (UTC)

• Mnbdawubos (talk · contribs · deleted contribs · nuke contribs · logs · filter log · block user · block log) Evidently a vandalism-only account - Created 7 minutes ago and has made two edits, both of which have been vandalism. interstatefive  03:01, 20 November 2024 (UTC)

  User has been incorrectly or insufficiently warned. Re-report if the user resumes vandalising after being warned sufficiently. — Red-tailed hawk _(nest) 03:11, 20 November 2024 (UTC)

• 184.71.182.54 (talk · contribs · deleted contribs · filter log · WHOIS · RDNS · RBLs · http · block user · block log) IP likely belongs to St. Thomas More Collegiate, has history of vandalism - see edit history Michael Reyes (talk) 03:07, 20 November 2024 (UTC)

  Insufficient recent activity to warrant a block. No edits in a month; not sure what this report is about. --Chris | Crazycomputers (talk) 03:24, 20 November 2024 (UTC)