I think I have been hacked, I'm not sure, how do I check?

This is a difficult question, since it depends on the type of the hack. As an indication, you can open up a few of the Source files (the files located in ./Sources) and see if there is any trace of base64_decode. If there is, there are chances that your forum has been hacked, and there are a few utilities and steps that help users to recover their SMF installation.

Another way of checking, although it's far less thorough, is to look at the datestamps on your files. If you haven't install any mods/themes, recently, yet some of your files show as being edited, recently, chances are that they've been modified by someone who shouldn't do.

Another method is to use the kb_scan.php tool. Please check the topic and follow its instructions.

I am sure I have been hacked...what do I do now?

First of all, keep calm. When the forum has been hacked, there are a few simple steps the administrator can perform.

• Backup your database.
  One of the most critical steps is to make backups of the whole SMF system, including the database. If the user has not yet made a backup of the database, he/she should do right now. If something goes wrong, you always have a backup at hand.

• File a security report with SMF.
  If your forum was breached via a security weakness within SMF or an SMF mod, and not via a weakness in a non-SMF script, please report it to the SMF developers so the issue can be investigated and, if confirmed, patched. Please report Security issues here.
  
  For security reports to be more useful, and help discovering what the problem really is, please provide your webserver logs, and/or FTP logs. Usually, you can find these logs in your host's control panel, or in a folder called /logs in your account.

• Run the kb_scan.php tool.
  Simply upload the tool, attached to the topic, to the forum directory (the directory where SMF is located) via FTP (File Transfer Protocol, How do I use FTP?), and run it in the browser of the user's preference. The kb_scan utility may find infected files, and in case it does, it will also try to clean them up and recover them.
  
  Please pay attention, in this case, to your database. A hack that can be found by the kb_scan.php tool may have malicious insertions in the database, which kb_scan tries to remove. In case it fails, see the instructions in the topic on how to do it, manually, or post in the support boards for assistance.

• Restore a recent backup that you know to contain unaffected files.
  You may want to remove first, the affected files and folders, cleaning up your installation, to be sure there isn't any trace left of the malicious files.

• Re-upload SMF files.
  • If you don't have a recent backup of your files, or to make sure you have a clean set of files, you can re-upload the standard SMF package files. Before you do, it's better to clean up your installation as completely as possible, removing almost all SMF files from your installation folder.
  • You may want however to keep the attachments folder (eventually remove the index.php file from it), the Settings.php files, and the custom folders you may have, if any (i.e. if you have a gallery installed, you may want to keep the folder where the gallery pictures are).
  • Check the Settings.php files to make sure there isn't any leftover hack line, and remove it if it's there.
  • Download a Large Upgrade Pack (Go to the download site) for the version of SMF that the user is running.
  • Upload every file in the package, except the files required for upgrading (usually just upgrade.php and a few SQL files), using FTP (How do I use FTP?, note that uploading may take a while). Now the user has fresh files and can use their forum safely again.

I have cleared my hacked SMF installation, how can I prevent this from happening again?

Using the kb_scan.php tool the user can keep their files safe. The user can also install a security modification (Go to the modification site) to enhance the forums security level. Depending on the modification's features this can be more or less active against hackers.

Notify your host so they can make sure no other servers have been affected. When you report the hack to your host, ask them to check their logs to see who might have had access to your server, and get them to check your file permissions. With some hosts incorrect file permissions can leave files open for easier hacking.