WARNING: Bot killing Trojan in the wild with very bad intentions

happygeek 4 Tallied Votes 514 Views Share

The Ainslot.L Trojan appears to be much the same as any other at first glance; logging user activity and sending Gmail and Facebook passwords to the bad guys, downloading further malware, taking over your computer and the main payload of being a Banking Trojan stealing account login data. But Ainslot.L has one rather more unusual trick up its sleeve in that it will also scan your system for evidence of other bot-related infections such as Zeus or DarkComet and remove any that it finds. Of course, Ainslot.L isn't doing this in order to cleanse your computer but rather to ensure that it is the only active bot and therefore getting all the gravy in terms of data and system resource access.

PandaLabs , the anti-malware research facility arm of vendor Panda Security, warns that Ainslot.L is distributed via a fake email which claims to be coming from a UK clothing company called CULT and takes the format of a 'you have placed the following order' social engineering scam. The sting being the link which supposedly allows the worried user, who has of course not ordered anything, view the order with a value of UKP 200 which it is claimed has been charged to your credit card. Clicking that link executes a download of Ainslot.L to the victims computer.

The bad guys in this case have done quite a good job of obfuscating their true intentions, with the file name of the executable being the same as the subject of the message itself together with the fake order number and implementing an Acrobat icon to fool the perhaps wary recipient into thinking it is 'just' a PDF document. This works well in terms of hiding true intent as most users don't think about changing system defaults that hide well known file extensions such as .exe and therefore wouldn't see it was something it is not. And once Ainslot.L is installed it will change your Registry settings to ensure it always executes when the computer starts, and to bypass the firewall, making it particularly problematical. Oh, did I mention that it names this additional Registry value to 'Windows Defender' so as to make it less likely someone would think it was anything but kosher.

Luis Corrons, technical director of PandaLabs, warns: "the fact that Ainslot.L removes other bots from infected systems definitely caught our attention. It eliminates all competition, leaving the computer at its mercy. It reminds us of the popular Highlander movies 'There can be only one'. Phishing emails are not usually so well done. There is no doubt that this time fraudsters have been very careful to try to make these messages look as real as possible to get as many bites as they can."

Philippe.Lahaie commented: love it! thanks for the read :) +6

Dani AI

Generated

Good catch by and a reasonable follow-up from — below is a compact, practical containment-to-recovery checklist you can apply to any suspected bot/malware infection. Follow steps in order; if the machine hosts sensitive accounts or you’re unsure, preserve an image and get professional help.

  1. Contain first — disconnect the PC from the network (unplug Ethernet, turn off Wi‑Fi). Avoid logging into online accounts from that machine.
  2. Preserve evidence — make a full disk image if possible (use a separate, write‑protected drive). This keeps forensic options open if the infection matters legally or financially.
  3. Scan from trusted media — boot a clean rescue USB/DVD and run offline scans from reputable on‑demand engines. Offline scanning helps find files or drivers that hide while Windows is running.
  4. Inspect persistence points — from a trusted environment check startup items, scheduled tasks, drivers/services, browser extensions and the hosts file (tools such as Sysinternals Autoruns and Process Explorer are useful for manual inspection).
  5. If removal is not certain, rebuild — for malware that steals credentials or hooks deep into the system, a full wipe and OS reinstall is the safest option. Only restore user files after scanning them from a known‑clean machine or backup.
  6. Recovery steps — change all passwords and rotate any sensitive credentials from a different, clean device; enable two‑factor authentication where available; notify banks or providers if account compromise is possible; monitor statements and logs.
  7. Prevention — keep systems and apps patched, use least‑privilege accounts, maintain offline backups, and apply basic phishing/email caution.

This expands on the alert in the thread with actionable steps you can use now. If there is doubt about cleanup success, treat the machine as compromised and rebuild.

Lucaci Andrew 140 Za s|n

So, is there any way we can ensure our safety, and if so, find out this Trojan, and delete it, cleaning our system?

happygeek 2,411 Most Valuable Poster Team Colleague Featured Poster

Most security vendors will have added signatures to cover this Trojan by now, some have free online scanners to check for it as well.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.