Fandom

Virus Information

LamerExterminator

247pages on
this wiki
Add New Page
Talk0 Share
LamerExterminator
Type Boot sector virus
Creator
Date Discovered 1989.10
Place of Origin Elmshorn, Germany
Source Language
Platform Amiga OS
Infection Length 1,024 bytes
Reported costs

LamerExterminator is an Amiga boot sector virus.

BehaviorEdit

When a disk infected with LamerExterminator is booted, the virus will load itself into memory. It will install itself to any disk that is accessed. The virus is encrypted, and if it is not in memory, it will show the encrypted virus when the boot sector is read. If the virus is in memory when the boot sector is read, it will show the original clean boot sector.

LamerExterminator has a damage routine that will activate at any reset or disk access. It overwrites bootblocks 84 times with the string "LAMER!". This will cause a read-write error n the disk.

VariantsEdit

  • LamerExterminator.2 through 8
  • Clist- also known as Lame Style U.K., as it is probably from Britain.
  • Guardians- overwrites the bootblock with "HIV". It is not encrypted.
  • IngosReturn- overwrites bootblocks with "FUCK!!". It gets its name from the text contained in the virus code: "INGO`S RETURN"
  • MadIV- overwrites bootblocks with "MAD".
  • Starcom 4- overwrites bootblocks with "STC!". The virus contains the text "A touch of STARCOM virus!".
  • Starcom Return- same as Starcom 4, but contains the text "The Return of STARCOM!!!!".
  • TAI 7
  • Hilly

NameEdit

LamerExterminator gets its name from the text contained in the viral code. It is sometimes also called "Lamer", partly because LamerExterminator is an unusually long name for a virus and also because it overwrites bootblocks with "LAMER!".

SourcesEdit

Computer Virus Catalog, 54 AMIGA Viruses.

Amiga Virus Encyclopedia, The Lamer Exterminator.

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.