Anyone can help! Whenever you spot a page that has been vandalised, you are encouraged to edit it and clean it up, and/or warn the vandal using an appropriate warning template. See What to do if you spot vandalism below.
If you find yourself cleaning up vandalism frequently, you might be interested in patrolling recent changes. Note that participation is entirely voluntary. Also, you are not required to enlist anywhere.
There are various tools to help you. See the Tools section below.
1. Revert the vandalism by viewing the page's history and selecting the most recent version of the page prior to the vandalism. Use an edit summary such as 'rvv' or 'reverted vandalism' and click on the button "Save page".
See also the section below for tools to help with reverting.
2. Warn the vandal. Access the vandal's talk page and warn them using an appropriate template.
See this overview of the most commonly used warning templates and this table for a wider selection of warning templates.
3. Report vandals who continue to vandalise after having received a final warning. Most cases of vandalism should be reported to WP:AIV. Cases that are not simple vandalism can be reported to WP:AN/I. WP:LTA may be used for reporting particular vandals who persistently return (e.g. via sockpuppets).
The old school way is to load recent changes and check the (diff) links. It can be filtered according to featured articles, good articles, living people, new editors' contribs, IPs' contribs and mobile contribs (as these are more prone to vandalism, see Help:Recent changes). Searching for articles by their namespace and specific tags (e.g. VisualEditor, possible BLP issue or vandalism, etc) can also be done. If they contain harmful edits, you revert to the previous version. However, the high volume of edits that occur each second makes this difficult to accomplish most of the time, and several tools have been created to simplify the process:
Vandal Fighter, the original anti-vandalism program, is a Java program that displays the Recent Changes feed from Wikipedia's IRC bots and allows filters to focus on certain types of changes (e.g. unregistered users). It also maintains a personal list of trusted users, watched articles, etc.
Lupin's Anti-Vandal Tool monitors the RSS feed and flags edits with common vandalism terms. It also has a live spellcheck feature. This tool works in monobook skin only.
WikiMonitor is a Windows program that enables users to monitor recent changes, their watchlist, users' contributions, and other feeds in real time as well as providing multiple tools to aid in semi-automated editing and reversion. It is compatible with all Wikimedia wikis.
VandalSniper, a VandalProof-like application, is currently in beta. At the moment it has only been confirmed to run on Linux.
WikiGuard is a Mac OS X program that monitors the IRC feed and attempts to approximate each edit's risk.
RC birds is a Java program that emits different bird sounds for the RC feed depending on the user.
The IRC Bot, pgkbot, by Pgk, runs on the IRC channels below.
IRC Bots reporting at the #cvn-wp-en channel on the freenode network list suspected vandalism edits (for example: blankings, edits made by blacklisted users, etc.) (Use this link to open the IRC channel on a web browser.)
WikiAlerter, a Windows program for patrolling new pages, and deleting/tagging them. Designed primarily for CSD, but supports AfD and ProD. Currently in beta, but there is a release.
Huggle is a very fast diff browser which parses edits from users and sort them by predicted level of vandalism. It allows you to revert vandalism and warn users in one click. Given the high performance and potential damage that could be caused by Huggle, users on English Wikipedia are required to have the rollback rights to login to huggle, however Huggle works even without this permission on other wikis.
WatchlistBot is an XMPP bot that sends messages in realtime when articles are modified. Users with a Jabber account can subscribe to the bot and watch both articles and users.
WikipediaVision is a web-based world map visualization of unregistered edits to the English (and the German, French, Spanish, Swedish) Wikipedia, almost the same time as they happen.
STiki is a Java program that consists of (1) a server-side component that listens to the RC feed and scores edits in a machine-learning fashion (using 12+ features, many of which are not language-based) -- and (2) A client-side Java GUI application that presents likely vandalism found on the server-side to human users for inspection/reversion. Using STiki without rollback requires either approval from the developer or 1000 article-space edits. It can revert WP:AGF edits while leaving a friendly message on the talkpage of the editing user.
These tools can be used to achieve the same effect as rollback if you do not have it.
RC patrol script gives non-administrators revert, filter, and popup tools while using the monobook skin.
Navigation popups are a set of utilities that appear when hovering over wikilinks. Particularly, hovering over links of old versions provides a "revert" link.
Twinkle gives both non-administrators and administrators three types of rollback functions. Other functions include a full library of speedy deletion functions, user warnings, pseudo-automatic reporting of vandals, and more.
#cvn-wp-en-cluenet Channel that reroutes information from ClueNet. (Read-only, only staff and bots can speak)
Template:Vandalism information, a tool used as an indication of the current overall level of vandalism that is taking place on Wikipedia. On the page, click the edit button below the vandalism meter to change its level from 5 to 1 and/or add a short comment; 5 indicates very low levels of vandalism, and 1 indicates extremely high. You can add the vandalism information template to your userpage to stay up to date. See Template talk:Vandalism information for different styles.