Date Summer 1998Founded UnknownSubmitted By GLSource AOL-Files.com/FDO-Files.com Archive The AIM registration process allowed 2 char screen names to be created along with indented screen names. Indents could be over the 2 character limit present in the recent indent exploit. Several of these screen names with 3 or more spaces indented still exist today along with several of the 2 char AIM’s made using this hole.

Date January 1998Founded Slushie and UaertSubmitted By O0OSource AOL-Files.com/FDO-Files.com Archive Slushie and Uaert found that the Rw token was not viewruled nor rostered. By sending the Rw token and an arg such as 56-2923 you could pull up the Examine Object Info for the token. EOI is used mainly in conjunction with Rainman and was valuable because it gave information on who created the object, which tokens linked to.....

Date 1998Founded unknownSubmitted By GLSource AOL-Files.com/FDO-Files.com Archive By going to kw:names and typing “blahblahAO” and pressing enter, it will return something like “blahblahAO19837″ and “AO1″ is a restricted prefix. You could also make TO5 in the same manner.

Date 2000Founded Rikky?Submitted By Tau and Pure (who submitted similar information)Source AOL-Files.com/FDO-Files.com Archive Dead, aka “ded”, screen names are screen names that can be accessed even though they technically belong to no account. The drawbacks are that you cannot send mail from them and that it takes a few steps to do. Here you will learn how to do it in 3 easy steps. No special tools are required......

Date December 10, 2000Founded EvergraceSubmitted By O0O and rogersSource AOL-Files.com/FDO-Files.com Archive AOL added a new feature to the kw: Names sub-account creation proccess. If a screen name you wanted was unavailable a form would come up asking you to enter three words and then AOL would automatically make an SN for you based on these three words. The n* token which ran this process did not have a restricted.....

Date 1997Founded UnknownSubmitted By CJSource AOL-Files.com/FDO-Files.com Archive This ‘exploit’ allowed users to send completely blank IMs, which also removed the screen name of the sender from the IM window. This trick was used by various punter programs so that you could not copy/paste any screen name from the IM window to make a report to CAT. To do this, you needed to send an IM with just (A HREF).....

Date 1997Founded Tang, LyriX and othersSubmitted By HypahSource AOL-Files.com/FDO-Files.com Archive In 1997, people in macfilez saw Tang, LyriX, and others get 23 copies of the exact same screen name in one room. Quite simple, really…you would connect, block the SC token, enter a room, then disconnect and repeat. Each connection added the name to the room. AOL fixed this in private rooms first, then later, conference rooms. Then, entering.....

Date Fall 1997Founded Lithium NodeSubmitted By O0OSource AOL-Files.com/FDO-Files.com Archive This was the first star tool to be discovered since early 1996. It was also the first for the newer 32 bit versions of AOL software designed for Windows 95. It had an Atomic Debugger integrated into master.aol. This was far stabler than the stand alone debugger being used for AOL 2.5/3.0 16 bit. It was found in the MMDev file.....

Date Summer 1997Founded Lance of Lithium NodeSubmitted By O0OSource AOL-Files.com/FDO-Files.com Archive Lance created the first major PC FDO file. Done completely in FDO it did not feature any major programming tricks but it was the first FDO file to feature links, etc in listboxes and buttons programmed using FDO.
Star Tool AOL 2.5/3.0 16 bit

Date 1996Founded Unknown, Hexed and Released by Mad MiserySubmitted By O0OSource AOL-Files.com/FDO-Files.com Archive This was a huge discovery for PC AOLers. Up until this point PCers were unable to do the things Mac hax0rs were able to with their version of the Star Tool, called Utilities. The Star tool for 16 bit AOL clients came with a limited Atomic Debugger and an invoker for f1 tokens. Within weeks of.....
Generating OH/Invoice/Internal Certs

Date 1995-96Founded UnknownSubmitted By O0OSource AOL-Files.com/FDO-Files.com Archive Using any internal account it was possible to generate OH/Invoice/Internal certs as long as you had a valid promo code for those account types. There was also a separate tool which allowed a cert to be rearmed. This resulted in hundreds of unauthorized OH accounts and many invoice and internal accounts being created. AOL patched this sometime in 1996 and now you.....