Red Teaming in the Financial Sector

Because of the invaluable data they possess, financial institutions remain a favorite target of malicious actors, with cyberattacks in the sector up more than 400% in three years. Fortunately, offensive security measures like red teaming can augment defensive tactics, giving security teams in the financial sector an additional leg up. Red team engagements test an […]

Read More… from Red Teaming in the Financial Sector

Cobalt Strike 4.11: Shhhhhh, Beacon is Sleeping….

Cobalt Strike 4.11 is now available. This release introduces a novel Sleepmask, a novel process injection technique, new out-of-the-box obfuscation options for Beacon, asynchronous BOFs, and a DNS over HTTPS (DoH) Beacon. Additionally, we have overhauled Beacon’s reflective loader and there are numerous QoL updates. Out-of-the-Box Evasion Overhaul The focus of this release (and the […]

Read More… from Cobalt Strike 4.11: Shhhhhh, Beacon is Sleeping….

Update: Stopping Cybercriminals from Abusing Cobalt Strike

Since 2023, Microsoft’s Digital Crimes Unit (DCU), Fortra, and the Health Information Sharing and Analysis Center (Health-ISAC) have been working together to combat the use of unauthorized, legacy copies of Cobalt Strike and compromised Microsoft software, which have been weaponized by cybercriminals to deploy ransomware  and other malware, causing significant harm to critical sectors like […]

Read More… from Update: Stopping Cybercriminals from Abusing Cobalt Strike

Cobalt Strike In 5 Minutes

Cobalt strike is a powerful red team tool that is used by pen testers and red teamers to replicate the tactics and techniques of long-term embedded attackers. This 5-minute video will give you a high-level overview of Cobalt Strike’s functionality, including its signature payload, Beacon, and its flexible C2 framework. Are you ready to take the next step? […]

Read More… from Cobalt Strike In 5 Minutes

Revisiting the UDRL Part 3: Beacon User Data

The UDRL and the Sleepmask are key components of Cobalt Strike’s evasion strategy, yet historically they have not worked well together. For example, prior to CS 4.10, Beacon statically calculated its location in memory using a combination of its base address and its section table. This calculation was then modified depending on the contents of […]

Read More… from Revisiting the UDRL Part 3: Beacon User Data