Note: articles are for educational purposes and are not professional security advice — consult an expert for your specific needs.

Silent Skimmer Campaign: Financial Data Theft

In short

Silent Skimmer exploits CVE-2019-18935 in Progress Telerik UI for ASP.NET AJAX to gain remote code execution and steal financial data. The campaign targets online businesses and Point-of-Sale (PoS) providers using ASP.NET and IIS across APAC and North America. Patch the vulnerability and monitor servers and applications for suspicious activity.

Summary written with AI from this article, and checked against it.

Unveiling the Silent Skimmer Campaign: A Cyber Threat to Financial Data

Affected systems and impact

FlawAffected systemsImpact
CVE-2019-18935Not statedProgress Telerik UI for ASP.NET AJAX; internet-facing applications using ASP.NET and IISRemote code execution on the compromised server

In the dynamic world of cybersecurity, the emergence of sophisticated threat actors like the Silent Skimmer represents a significant challenge. This article delves into the details of the Silent Skimmer campaign, a complex web-skimming operation targeting financial data across the APAC and NALA regions.

Overview of the Silent Skimmer Campaign

The Silent Skimmer, a financially motivated threat actor, has been conducting an extensive web-skimming campaign for over a year. This operation exploits vulnerabilities in internet-facing applications to steal sensitive financial data from users. Despite the unknown identity of the perpetrators, indications suggest a connection to a Chinese hacker group.

Technical Details of the Attack

The campaign commences by exploiting vulnerabilities in internet-facing applications, particularly focusing on those running ASP.NET and IIS. The threat actors utilize automated scanning tools to identify potential targets with the CVE-2019-18935 vulnerability in Progress Telerik UI for ASP.NET AJAX. This vulnerability allows remote code execution on the compromised server.

Upon breaching the security, the attackers deliver a malicious Dynamic Link Library (DLL) to the server. This DLL is crucial for the execution of unauthorized code and the deployment of various malicious tools stored on an HTTP File Server controlled by the attackers. These tools include downloader scripts, remote access scripts, webshells, exploits, and Cobalt Strike beacons.

The Exfiltration Process

The final stage of the attack focuses on exfiltrating sensitive user data, such as financial information and credit card details. To avoid detection, the data is routed through Cloudflare, concealing the data's origin and destination.

Geographic Scope and Target Selection

Originally targeting the APAC region, the campaign has recently expanded to North America, with a strategic focus on online businesses and Point-of-Sale (PoS) providers using ASP.NET and IIS.

Recommendations for Protection

  1. Patch Vulnerabilities: Address the CVE-2019-18935 vulnerability promptly to prevent initial access.
  2. Security Monitoring: Implement advanced monitoring to detect suspicious activities on servers and applications.
  3. Threat Intelligence: Stay informed about the Silent Skimmer's tactics and infrastructure through IOCs.
  4. Enhanced Authentication: Adopt multi-factor authentication and strong password policies.
  5. User Education: Train staff to recognize and report phishing attempts and unusual activities.

Conclusion

The Silent Skimmer campaign showcases the evolving nature of cyber threats, especially in the financial sector. With its expanded reach and sophisticated techniques, it poses a significant risk. Organizations must prioritize cybersecurity, update their systems, monitor their networks, and engage with the broader cybersecurity community to counteract these threats. By leveraging threat intelligence and understanding the attacker's methodologies, companies can better protect themselves from such advanced and persistent cyber-attacks.

Quick revision

Interview flashcards

  1. What is the objective of the Silent Skimmer campaign?

    Silent Skimmer is a financially motivated web-skimming campaign that exploits vulnerabilities in internet-facing applications to steal sensitive financial data from users.

  2. Which businesses and regions does Silent Skimmer target?

    Silent Skimmer focuses on online businesses and Point-of-Sale (PoS) providers using ASP.NET and IIS. It originally targeted APAC and has expanded to North America.

  3. How does Silent Skimmer gain initial access to servers?

    The attackers use automated scanning tools to identify CVE-2019-18935 in Progress Telerik UI for ASP.NET AJAX. This vulnerability allows remote code execution on the compromised server.

  4. What role does the malicious DLL play in a Silent Skimmer attack?

    The malicious Dynamic Link Library (DLL) enables unauthorized code execution and deployment of malicious tools stored on an attacker-controlled HTTP File Server.

  5. What tools does Silent Skimmer deploy after compromising a server?

    Silent Skimmer deploys downloader scripts, remote access scripts, webshells, exploits, and Cobalt Strike beacons. These tools are stored on an HTTP File Server controlled by the attackers.

  6. How does Silent Skimmer conceal the exfiltration of stolen data?

    The attackers route sensitive user data, including financial information and credit card details, through Cloudflare. This conceals the data's origin and destination to avoid detection.

  7. Which vulnerability should organizations patch to prevent Silent Skimmer's initial access?

    Organizations should promptly patch CVE-2019-18935 in Progress Telerik UI for ASP.NET AJAX. Addressing this vulnerability helps prevent initial access.

  8. How can organizations detect suspicious activity associated with Silent Skimmer?

    Organizations should implement advanced monitoring on servers and applications to detect suspicious activities. Threat intelligence through IOCs can help them stay informed about Silent Skimmer's tactics and infrastructure.

Written with AI from this article, and checked against it.

Vishal

About the author

· Software & security engineer

GitHub · LinkedIn · X

Vishal writes Trickyworld's tutorials and interview-preparation guides on programming, databases, cyber security and AI. Vishal has been shipping production software long enough to have firm opinions about Python, PHP, Node.js, and JavaScript, and to have been wrong about each of them at least once. The work has run the whole stack: Drupal and Laravel applications, React front ends, MySQL and MongoDB underneath, Redis and Memcached for the things that had to be fast, Apache Solr for the things that had to be findable. That last part turned out to matter more than anyone expected. Tune a Solr index for a season, then watch a language model confidently retrieve the wrong document, and you recognise an old problem wearing new clothes. Most of what is hard about AI systems is not the model. It is retrieval, caching, latency budgets, and deciding what the system does when the answer comes back wrong — which is work he has been doing since well before anyone called it AI engineering. He plays a lot of games, which is less a hobby disclosure than an admission of where a good share of his engineering instinct came from. Real-time systems with a frame budget. State that has to stay coherent while a player does something no designer anticipated. The permanent question of what happens when the frame cannot finish in time. Those habits carry over more directly than they have any right to. He has written several books on programming, all built on the same conviction: most technical writing is unclear because the author never decided what to leave out. More from Vishal → · Editorial policy

#NALA#ASP.NET#IIS#payment companies#APAC#financial data theft#CVE-2019-18935#Silent Skimmer campaign#cybersecurity#web-skimming#.NET deserialization vulnerability

More on Cyber Security.

Latest articles

$ subscribe --weekly

Get the next tutorial in your inbox.

Programming, security and AI — the practical bits, no spam. Unsubscribe any time.