DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Duqu Authors Sprinkle Humor in Dangerous Code

Posted on November 12, 2011 by Lee J

Wrapped in the code used to infect computers is an "Easter egg," or a hidden message. Easter eggs have long been inserted in computer code, often seen only by those who enjoy browsing computer code. Duqu’s exploit, the code used to take advantage of a software vulnerability, contained the line: "Copyright (c) 2003 Showtime Inc. All rights reserved. DexterRegularDexter." The reference to the television show "Dexter" is meant as a joke. The shellcode of the exploit is contained in an embedded font called "DexterRegularDexter," which is processed by Windows’ Win32k TrueType font parsing engine, wrote Aleks Gostev, a senior analyst with the Global Research and Analysis Team for Kaspersky Lab. "This is another prank pulled by the Duqu authors," he wrote. There actually is no font called Dexter, though, and it is just a name the malware authors assigned to the file, said Costin Raiu, director of Kaspersky’s Global Research and Analysis Team. Kaspersky and many other computer security companies have been analyzing Duqu since it surfaced. Duqu shares some similarities with Stuxnet, the malware believed to have been created with the intention of disrupting Iran’s nuclear program by tampering with centrifuges used to enrich uranium. But experts remain uncertain if there is a connection between the developers of the two pieces of malware. Gostev’s latest write up is an analysis of a version of Duqu that came from Sudan’s CERT (Computer Emergency Response Team), which had a sample of Duqu from an unnamed organization that was infected. Victims are infected by an exploit delivered via a tampered Microsoft Word document, which, if opened, delivers Duqu. Gostev’s post includes a screenshot of the simple email purporting to come from a marketing manager, "Mr. B. Jason," requesting that the receiver open a Word document and answer a few questions such as "Do you supply marine shipping?" Other clues in the code have indicated that Duqu could be as much as 4 years old. A driver loaded by Duqu’s exploit into the Windows kernel has a date saying it was compiled on Aug. 31, 2007, Gostev wrote. But that may not be accurate, since Duqu has different components that could have been created at different times. Another oddity discovered by Kaspersky is how often attacks occurred on Wednesdays. "The Duqu gang has an affinity for Wednesdays,"Raiu said. "They have repeatedly attempted to steal information from these systems on Wednesdays. This probably indicates a strong routine, almost military type." The attackers also took a lot of care when they struck to avoid being detected. They used separate command-and-control servers for each unique set of files. They also crafted a unique Word file for each victim and sent the malicious files from anonymous e-mail accounts, probably on compromised computers, Gostev wrote. They even modified the shellcode for different attacks. The evidence points to a high level of sophistication. "The exploit used to infect victims with Duqu is incredibly well written, beautiful in a sense," Raiu said. "The Duqu authors are top-class exploit writers."


Related:

  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Attorney General James Secures $14.2 Million from Car Insurance Companies Over Data Breaches
Category: Breach Incidents

Post navigation

← Computer virus hits NZ ambulances
Steam hit by hackers →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.