GoFetch: Apple CPU encryption hack | Kaspersky official blog

In mid-March, researchers from several U.S. universities published a paper demonstrating a hardware vulnerability in Apple’s “M” series CPUs. These CPUs, based on the ARM architecture and designed by Apple, power most of its newer laptops and desktops, as well as some iPad models. The issue could potentially be exploited to break encryption algorithms. The attack that uses this vulnerability was dubbed “GoFetch”.

The combination of a juicy topic and a big-name manufacturer like Apple led to this highly technical paper being picked up by a wide range of media outlets — both technical and not so much. Many ran with alarmist headlines like “Don’t Trust Your Private Data to Apple Laptops”. In reality, the situation isn’t quite that dire. However, to really get to the bottom of this new problem, we need to delve a little into how CPUs work — specifically by discussing three concepts: data prefetching, constant-time programming, and side-channel attacks. As always, we’ll try to explain everything in the simplest terms possible.

Data prefetching

The CPU of a desktop computer or laptop executes programs represented as machine code. Loosely speaking, it’s a bunch of numbers — some representing instructions and others representing data for calculations. At this fundamental level, we’re talking about very basic commands: fetch some data from memory, compute something with this data, and write the result back to memory.

You’d think these operations should be executed in this order. Here’s a simple example: a user enters their password to access a cryptocurrency wallet. The computer needs to read the password from RAM, run a few computing operations, check that this is the correct password, and only then grant access to the confidential data. If this were the way today’s CPUs executed all code, our computers would be painfully slow. So how do you speed things up? You do a lot of optimization — such as data prefetching.

Data prefetching works like this: if the program code contains a command to fetch data, why not load it ahead of time to speed things up? Then, should the data come in handy at some point, we’ve just made the program run a bit faster. No big deal if it doesn’t come in handy: we’d just discard it from the CPU’s cache and fetch something else.

That’s how basic data prefetching works. Apple CPUs make use of a newer prefetcher known as “data memory-dependent prefetcher”, or DMP. In a nutshell, DMP is more aggressive. Commands to fetch data from memory are not always explicit. Pointers to specific memory locations might be the result of computing work that still needs to be performed, or they might be stored in a data array that the program will access later. DMP tries to guess which data in the program is a pointer to a memory location. The logic is the same: if something looks like a pointer, try fetching data at that address. The guessing process relies on the history of recent operations — even if they belong to a completely different program.

In 2022, another study demonstrated that DMP tends to confuse pointers with other data the program is working with. This isn’t necessarily a problem by itself — loading the wrong stuff into the CPU cache isn’t a big deal. But it becomes a problem when it comes to encryption algorithms. DMP can break constant-time programming under certain conditions. Let’s talk about this next.

Constant-time programming

There’s a simple rule: the time it takes to process data must not depend on the nature of that data. In cryptography, this is a fundamental principle for protecting encryption algorithms from attacks. Often, malicious actors try to attack the encryption algorithm by feeding it data and observing the encrypted output. The attacker doesn’t know the private key used to encrypt the data. If they figure out this key, they can decrypt other data, such as network traffic or passwords saved in the system.

Poor encryption algorithms process some data faster than others. This gives the malicious actor a powerful hack tool: simply by observing the algorithm’s runtime, they can potentially reconstruct the private key.

Most encryption algorithms are immune to this type of attack: their creators made sure that computing time is always the same, regardless of the input data. Algorithm robustness-tests always include attempts at violating this principle. This is what happened, for example, in the Hertzbleed attack. However, to make actual key theft possible, the attack must use a side channel.

Side-channel attack

If DMP prefetching sometimes confuses regular application data with a memory pointer, does that mean it can mistake a piece of a private key for a pointer? It turns out it can. The researchers demonstrated this in practice using two popular data encryption libraries: Go Crypto (Go developers’ standard library), and OpenSSL (used for network traffic encryption and many other things). They investigated various encryption algorithms — including the ubiquitous RSA and Diffie-Hellman, as well as Kyber-512 and Dilithium-2, which are considered resistant to quantum computing attacks. By trying to fetch data from a false pointer that’s actually a piece of a private key, DMP essentially “leaks” the key to the attacker.

There’s one catch: the hypothetical malware needed for this attack has no access to the cache. We don’t know what DMP loaded there or which RAM address it fetched the data from. However, if a direct attack isn’t possible, there’s still a chance of extracting information through a side channel. What makes this possible is a simple feature of any computer: data loaded into the CPU cache is processed faster than data residing in regular RAM.

Let’s put this attack together. So, we have malware that can feed arbitrary data to the encryption algorithm. The latter loads various data into the cache, including a secret encryption key. DMP sometimes mistakenly fetches data from an address that’s actually a piece of this key. The attacker can find out indirectly that data has been prefetched from a certain address by measuring the time it takes the CPU to access certain pieces of data: if the data was cached, accessing it will be slightly faster than otherwise. This was exactly how the researchers broke the constant-time programming principle: we can feed arbitrary text to the algorithm and watch the processing time vary.

So, is your data at risk?

In practice, extracting an encryption key requires dozens to hundreds of thousands of computing operations as we feed data into the algorithm and indirectly monitor cache status. This is a sure-fire attack, but a very resource-intensive one: stealing a key takes an hour at best — more than ten hours at worst. And for all this time, the computing effort will keep the device running almost at full capacity. The GoFetch website has a video demonstration of the attack, where the private key is extracted bit by bit — literally.

Screenshot from the research demo video. Source

However, that’s not what makes the attack impractical. We’ve repeatedly mentioned that the attack requires malware to be installed on the victim’s computer. As you can imagine, if this is the case, the data is already compromised by definition. There are likely far simpler ways to get to it at this point. This is the reason why the OpenSSL developers didn’t even consider the researchers’ report: such attacks fall outside their security model.

All studies like this can be compared to civil engineering. To make a structure robust, engineers need to study the characteristics of the materials to be used, the given location’s soil properties, make provisions for the risk of earthquakes, and do many other things. In most cases, even a poorly constructed building will stand for decades without problems. However, a rare combination of circumstances may lead to disaster. Attack scenarios like GoFetch are designed to avert such disasters that lead to mass leaks of user secrets.

The researchers are going to continue studying this fairly new prefetching mechanism. Intel processors also use it starting with the 13th generation, but they’ve proved insusceptible to this particular kind of attack proposed in the research paper. What’s important is that the vulnerability can’t be patched: it will continue to affect Apple’s M1 and M2 CPUs for their entire lifespan. The only way to prevent this type of attack is by modifying encryption algorithms. One possibility involves restricting the calculations to the CPU’s “energy-efficient” cores, as DMP only works on “high-performance” cores. Another one is obfuscating encryption keys before loading them into RAM. A side effect of these methods is performance degradation — but the user would hardly even notice. In turn, Apple M3 CPUs feature a special flag that disables DMP optimization for particularly sensitive operations.

Let’s summarize. There’s no immediate threat to data stored on Apple devices — hardly anyone would try using a technique this complex to steal that data. Nevertheless, the work of these U.S. researchers is still valuable because it sheds some light on hitherto-unknown operating aspects of how the latest CPUs work. Their efforts aim to prevent future problems that might arise if an easier exploit is discovered.

Kaspersky official blog – ​Read More

How to tell that what appears to be a message from your boss is actually the beginning of a scam attack | Kaspersky official blog

Imagine getting a call or message from your immediate senior — or maybe even the head honcho of the whole company. They warn you about a nasty situation brewing. It spells fines or some other financial woes for the company, big trouble for your department, and possible dismissal for you personally! Cold sweat trickles down your spine, but there’s still a chance to save the day! You’ll have to hustle and do a few things you don’t usually do, but everything should be alright…

First – hold your horses and take a few deep breaths. There’s a 99% chance this whole “emergency” is completely made up and the person on the line is a scammer. But how do you recognize such an attack and protect yourself?

Anatomy of the attack

These schemes come in dozens of flavors. Scammers may describe various issues faced by your company depending on the particular country, cite involvement of regulators, police, or major business partners, and then suggest all manner of ways to “solve the problem” with your help. Yet there are a number of key points — crucial psychological footholds — without which the attack is next to impossible to carry out. These can be used to recognize the attack for what it is.

The superior’s authority, or simple trust in someone you know. Most people by now have developed a resistance to odd requests from strangers — be it a police officer who’s decided to reach out through instant messaging, or a bank employee personally concerned about your wellbeing. This scheme is different: the person approaching the victim appears to be someone you know to some extent — and a fairly important person at that. Scammers often choose a C-level manager’s profile as bait. First, they have authority; second, chances are the victim knows the person, but not well enough to spot the inevitable differences in speech or writing style. However, there are variations on this scheme where the scammers impersonate a coworker from a relevant department (such as accounting or legal) whom you may not know personally.
Redirection to an external party. In the most primitive cases, the “coworker” or “manager” who reaches out to you is also the person you get a request about money from. Most often though, after the initial contact, the “boss” suggests you discuss the details of the matter with an external contractor who’s about to reach out. Depending on the scheme’s specifics, this “assigned person” may be introduced as a law enforcement or tax officer, bank employee, auditor or similar; i.e., not someone the victim knows. The “boss” will ask you to provide the “designated person” with all the assistance they’ll need and without delay. That said, the most elaborate schemes, such as the one with $25 million stolen following a deepfake video conference, may have the scammers pose as company employees throughout.
A request has to be urgent, so as not to give the victim time to stop and analyze the situation. “The audit is tomorrow”, “the partner’s just arrived”, “the amount gets charged this afternoon”… long story short, you have to act right now. Scammers will often conduct this part of the conversation by phone, telling the victim not to hang up until the money is transferred.
Absolute secrecy. To prevent anyone from interfering with the fraud, the “boss” early on warns the victim that discussing the incident with anyone is strictly forbidden as disclosure would lead to disastrous consequences. The fraudster might say that they’ve no one else to trust, or that some of the other employees are criminals or disloyal to the company. They will generally try to keep the victim from talking to anyone until their demands are met.

Example of a scam email from a fake boss

Objectives of the attack

Depending on the victim’s position and level of income, an attack may pursue different goals. If the victim is authorized by the company to execute financial transactions, the scammers will try to talk them into making an urgent secret payment to a vendor such as a law firm for assistance in solving problems — or just transferring the company’s money to a “safe” account.

Employees who don’t deal with the company’s money can be targeted by attacks that seek to obtain company data such as passwords to internal systems, or their own funds. Scammers may come up with dozens of backstories, ranging from an accounting data leak that jeopardizes the victim’s account, to a need to keep the company’s cash gap closed until an audit is done. In the latter case, the victim is asked to use their own money in some way: transfer it to another account, pay for gift cards or vouchers, or withdraw it and give it to a “trusted person”. For greater persuasiveness, the scammers may promise the victim generous compensation for their expenses and effort — only later.

Convincing level of detail

Social media posts and numerous data leaks have made it much easier for fraudsters to launch carefully prepared, personalized attacks. They can: find the full names of the victim, their immediate senior, the CEO, and employees in the relevant departments (such as accounting), along with the exact department names; and find pictures of these individuals to create convincing instant messaging profiles and, if needed, even voice samples to create audio deepfakes. If there’s big money at stake, the scammers may invest significant time in making the charade as convincing as can be. In some previous cases, attackers even knew the locations of company departments inside buildings and the positions of individual employees’ desks.

Technical side of the attack

Sophisticated schemes like this nearly always include a phone call from the scammers; however, the initial “call from the boss” may also come in the form of an email or instant message. In simpler versions of the attack, the scammers just create a new instant messaging or email account with the manager’s name, while in more sophisticated cases they hack their corporate email or personal accounts. This is called a BEC (business email compromise) attack.

As for phone calls, scammers often use number spoofing services or obtain an illegal copy of the SIM card — the victim’s caller ID then displays the company’s general phone number or even their boss’s own.

Malicious actors may use deepfake voice generators, so a familiar voice on the other end of the line can’t guarantee the caller’s authenticity. Schemes like these may even use video calling where the caller’s face is also a deepfake.

Protecting yourself against scammers

First and foremost, attentiveness and courage to verify the information despite the scammers’ threats are two things that can protect you against this kind of attack.

Take it slow, and don’t panic. The scammers aim to knock you off balance. Keep calm and double-check all the facts. Even if the other party insists you don’t hang up the phone, you can always pretend that the call dropped. This will buy you some time to do more fact-checking.

Pay attention to the sender’s address, phone, and user name. If you’re used to corresponding with your boss by email, but then you suddenly get an instant message in their name from an unfamiliar number, it’s time to prick up your ears. If you’ve always talked on an instant messaging app and you get a new message but there’s no history, this means someone’s using a newly created account, which is a major red flag. Unfortunately, cybercriminals sometimes use fake email addresses that are hard to tell from the real ones, or hacked email or instant messaging accounts. All of this makes detecting forgery much more difficult.

Pay attention to small details. If a person you know approaches you with an odd request, is there anything about the situation that tells you that the person may be an impostor? Do their emails look slightly unusual? Are they using uncharacteristic figures of speech? Do you usually address each other by first names, but they’re using a formal form of address? Try asking them something only the real person could know.

Raise a red flag if you get an unusual request. If your boss or coworker is urgently asking you to do something unusual — and to keep it a secret to boot — this is nearly always a sign of a scam. Therefore, it’s critical that you verify the information you get and confirm the other party’s identity. The least you can do is contact that person using a different channel of communication. Talking in person is best, but if this isn’t a possibility, call their office or home number that you’ve got down in your phone book, or punch in that number manually; don’t just dial the last incoming number — to avoid circling back to the scammers. Use any other channels of communication available. The cell number that called you — even if it’s your boss or coworker’s real number you’ve gotten saved in your phone book — might have been compromised through SIM swapping or simple phone theft.

Check with your coworkers. Despite being asked to “keep it all confidential”, depending on the nature of the request, it doesn’t hurt to verify the information with your coworkers. If you get what appears to be a message from someone in accounting, contact other people in the same department.

Warn your coworkers and law enforcement. If you receive such a message, it means scammers are targeting your organization and coworkers. If their tricks don’t work on you, they’ll try the next department. Warn your coworkers, warn security, and report the attempted scam to the police.

Kaspersky official blog – ​Read More

Eavesdropping on keyboard keystrokes | Kaspersky official blog

U.S. researchers recently published a paper demonstrating that useful information can be extracted from the sounds of keystrokes. This is certainly not the first study of its kind; moreover, the results can’t even be considered more accurate than the conclusions of its predecessors. However, what makes this one interesting is that the researchers weren’t aiming for perfect, lab-controlled conditions. Instead, they wanted to see how it works in fairly realistic conditions: a somewhat noisy room, a not-so-great microphone, and so on.

Attack model

We often get eavesdropped on without even realizing it. And I’m not referring to spy movie clichés with bugs planted in offices and hotel rooms.

Imagine you’re stuck in a boring conference call at work and, at the same time, you’re discreetly catching up on work emails or personal messages without muting your microphone. Guess what? Your colleagues can hear your keystrokes. Streamers — those who love broadcasting their gaming sessions (and other stuff) — are also at risk. They might get distracted mid-stream and, for example, type a password on the keyboard. While the keyboard itself may not be visible, someone could record the sound of the keystrokes, analyze the recording, and try to figure out what was typed.

The first scientific study examining such an attack in detail was published in 2004. Back then, IBM researchers merely proposed a method and demonstrated the basic possibility of distinguishing one keystroke from another, but nothing more. Five years later in 2009, the same researchers attempted to solve the problem using a neural network: a special algorithm was trained on a 10-minute recording of keyboard input, with the text known in advance. This made it possible to associate specific keystroke sounds with typed letters. As a result, the neural network recognized up to 96% of the characters typed.

However, this result was obtained in a lab-controlled environment. The room was completely silent, a high-quality microphone was used, and the text was typed more or less consistently (with roughly the same typing speed and keystroke force). Moreover, a loud mechanical keyboard was used. This study demonstrated the theoretical possibility of an attack, but its results were difficult to apply in practice: if you change the typing style slightly, change the keyboard, or add natural ambient noise to the room, recognition becomes impossible.

Real-life eavesdropping

Everyone has their own unique way of typing. The researchers found patterns in these individual styles, which helped them analyze the sounds of keystrokes. For instance, they discovered that people tend to type common letter pairs at a consistent speed. They also found that it’s fairly easy to distinguish individual words, since the sounds of the spacebar and Enter key are usually distinct from other keys.

During the experiments, the researchers assumed that the potential eavesdropping victim would be typing in an office with a normal level of background noise. Other than that, there were no special restrictions on the participants. They could use any keyboard and type however they wanted. The recording was done on a low-quality, built-in laptop microphone. For a successful attack, however, a potential spy needs to record a sufficiently long sequence of keystrokes — otherwise, it won’t be possible to train the neural network. The recording looks something like this:

Shape of the audio signal corresponding to certain keystrokes. Source

Each peak in amplitude corresponds to a specific keystroke. The pause between keystrokes may vary depending on the user’s typing skill and the sequence of letters being typed. In this study, the neural network was trained to recognize these pauses specifically, and as it turns out, they also carry a lot of information — no less than the differences in keystroke sounds themselves!

An important breakthrough in this new study was the use of the neural network to predict whole words. For example, if the neural network identifies the word “goritla” from the keystrokes, then we can confidently assert that the user actually typed “gorilla”, and there was just an error in recognition. The more letters in a word, the more accurately it can be guessed. This rule applies to up to six-letter words — beyond which the accuracy doesn’t increase.

A total of 20 volunteers participated in the experiment. First, they typed an already-known text, which was then correlated with the keystroke sounds and used to train the recognition algorithm. Next, the subjects typed a secret text, which the neural network tried to decipher based on the typing patterns and how well it matched real words. The accuracy varied from person to person, but on average the AI correctly guessed 43% of the text just from the keystroke sounds.

Side channels all around us

This is yet another example of a side-channel attack — when information is leaked indirectly. We’ve written a lot about such attacks. For example, here is a method of espionage using a light sensor. Here we talked about extracting sound from video data by analyzing tiny vibrations in the image. Phone conversations can be eavesdropped on using an accelerometer – the sensor built into every smartphone. The indirect channels of information leakage are indeed many.

But out of all these attacks, extracting text by analyzing keystroke sounds is the most viable in practice. When we enter a credit card number or password, we can hide the keyboard from prying eyes, but protecting yourself from eavesdropping isn’t so easy.

Of course, a 43% accuracy rate in guessing the text might not sound that impressive — especially considering it’s guessing whole words, not random characters like you’d expect in a password. Still, this new research is a significant step toward making this type of attack practical. It’s not quite there yet, but imagine someone in a café or on the train potentially stealing your password, credit card number, or even your private messages just by listening to you typing.

Perhaps future research will bring us closer to this dangerous scenario. But even now we can outline methods of protecting against such attacks and start applying them to particularly sensitive data right away. For starters, avoid typing passwords or other secret information during conference calls — especially during public online events. For many reasons, we recommend using two-factor authentication — it protects well against various password compromise scenarios.

Finally, there’s a way to counteract this specific side-channel attack. It’s based on the fact that you have a certain consistent pattern of typing on the keyboard. Want to make it harder for those sneaky hackers? Break the pattern: mix up your typing style. Both super-slow and super-fast typing can work wonders.

Kaspersky official blog – ​Read More

Transatlantic Cable podcast episode 340 | Kaspersky official blog

Episode 340 of the Transatlantic Cable podcast kicks off with news that the EU is investigating Meta, Apple and Google for “uncompetitive practices.” Additionally, the US government has gone ahead and levelled a lawsuit against Apple, for what they see as “monopoly” behaviour with their hardware.

To wrap up, the team discuss two stories, the first around China and UK government hacking concerns and how age-verification for adult sites could actually be a bad thing in the long run.

If you liked what you heard, please consider subscribing.

Apple, Meta and Google to be investigated by the EU
US sues Apple for illegal monopoly over smartphones
Beijing behind cyberattacks on UK MPs and peers, deputy PM to warn
The Dangers of Age Verification

Kaspersky official blog – ​Read More

Best Defense in 2024 | Kaspersky official blog

Choosing the right cybersecurity solution is no easy task. Friends’ opinions and/or crowdsourced ratings — which are great for simpler products and services — are less reliable. While these can help with assessing user interfaces and overall usability, they’re not much good for assessing the quality of protection against advanced threats.

The most balanced, objective source is independent expert research by specialized testing labs and media. Yes, independent — they must have no ties to any vendor whose products they evaluate whatsoever.

We’ve always take independent testing of our products and services seriously. And for a quick and easy way to evaluate just how well we’ve been doing down the years, our website has a Top-3 section, which shows the number of tests taken part in during a year, and in how many we podiumed.

2023 was a record year for us: out of precisely a hundred tests featuring our solutions, 93 times we came first, and 94 times finished in the top-three. And since 2013, our products have been tested by independent researchers a total of 927 times, claiming 680 first places (and 779 top-three finishes). This is the absolute record among all security solutions vendors both in terms of the number of tests and the number of victories.

Now for a little more detail.

Comparative chart with the results of independent security testing of popular vendors. Kaspersky is the absolute leader: 680 first places out of 927 tests conducted. Source

Most significant awards

Last year’s achievements are too numerous to list in their entirety, so we’ll highlight the most outstanding:

Kaspersky Standard was named Product of the Year by AV-Comparatives. So pleased were we, we even dedicated a separate blog post to the story.
Kaspersky Plus for Windows underwent all of SE Labs’ quarterly Endpoint Security: Home 2023 tests, and earned the highest total accuracy rating of 100% in all four of them.
Kaspersky Safe Kids was awarded Parental Control certification by AV-Comparatives for blocking at least 98 percent of pornographic websites with zero false positives on child-friendly websites.
Kaspersky Plus for Mac picked up its first Best MacOS Security Award for Consumer Users from AV-Test, with perfect results in its Mac security testing over the course of the whole year.
A trio of our products – Kaspersky Standard, Kaspersky Endpoint Security for Business and Kaspersky Small Office Security – won AV-Test’s Best Advanced Protection 2023 award for exceptional protection against APT attacks deploying ransomware and data stealers. These products also received the Best Usability 2023 award for the lowest number of false positives, the maximum score in all categories (including protection, performance, and usability), as well as the “Top Product” award based on AV-TEST’s results for Windows antivirus software for both home and business.
Kaspersky Endpoint Detection and Response gained recognition as “Strategic Leader” for achieving a 100% active response cumulative score in AV-Comparatives’ Endpoint Prevention & Response (EPR). The solution was also awarded AV-TEST’s Approved Advanced Endpoint Detection and Response Certification for demonstrating impressive coverage and valuable analytics in a study that involved a series of red-team attacks that replicated the tactics of both the Hafnium and Lazarus hacking groups. Additionally, the solution was recognized by SE Labs in its Enterprise Advanced Security (EDR) test, receiving the highest AAA rating for detecting all targeted attacks with no false positives.
Kaspersky Endpoint Security for Business and Kaspersky Small Office Security were awarded AAA ratings in all SE Labs’ Endpoint Security: Enterprise 2023 and Endpoint Security: SMB 2023 comparative tests, respectively.

Who does the testing?

For those unfamiliar with the world of cybersecurity testing, here’s a rundown of the key players.

AV-Comparatives is an independent Austrian organization that’s been testing security products for over 24 years. During this time, what started out as a student project at the University of Innsbruck has grown into one of the most influential research centers in cybersecurity.
AV-Test GmbH is an independent German information-security research institute. It has been advising industry associations, companies, and government agencies on cybersecurity for more than 15 years.
SE Labs is an independent UK company that has developed next-generation product testing based on a comprehensive approach to security assessment.

Alternative approach

Of course, besides serious testing labs, there are specialized media and bloggers that evaluate security software. Their research may be a little less meticulous, but in terms of the grabbing of users’ attention (aka “influencing”:), YouTubers and tech wordsmiths can’t be beat.

If this format floats your boat, we recommend checking out tests (for example, 1, 2 and 3) on the PC Security Channel, run by a UK-based YouTuber. The channel’s killer feature is the many tech gurus among its subscribers, who like to cast a critical eye over the posted content and add their own valuable observations.

Kaspersky official blog – ​Read More

Ways to detect and curb Living off the Land (LotL) attacks | Kaspersky official blog

Should serious-minded attackers choose namely your company to target, they’d certainly be looking to gain a long-term, persistent presence in your infrastructure. Some would deploy high-end malware to achieve this – but others prefer not to. Many, in fact, prefer to attack companies by exploiting vulnerabilities, stolen credential, and legitimate programs that are already in the system. This technique – known as Living off the Land (LotL) – has many advantages from an attacker’s point of view:

Malicious activity blends in with everyday network and administrative activities.
Tools already installed on computers are less likely to trigger endpoint protection (EPP).
There’s no need to spend time and resources on developing one’s own malicious tools.
Such activity doesn’t produce obvious indicators of compromise (IoC), making it hard to trace malicious activity and compare attacks across organizations.
Many companies fail to collect and store information about network monitoring and day-to-day network activity in sufficient detail, so it’s impossible to track the evolution of an attack in real time – much less historically. This makes preventing attacks and mitigating their consequences extremely tricky.

LotL tactics are used by various groups: spy groups (see here and here), money-minded cybercriminals, and ransomware gangs.

Environments prone to LotL attacks

LotL attacks can be carried out in any environment: cloud, on-premises, hybrid; on Windows, Linux, and macOS platforms. Incidentally, attacks on macOS are sometimes known as Living off the Orchard – a reference to, yes, apples. In each of these environments, attackers have a variety of tools and techniques at their disposal:

Tools useful to attackers are usually called LOLBins (LOL binaries) or LOLBAS (LOL binaries and scripts). We analyzed the most popular LOLBins; a more complete list of all Windows tools seen in attacks can be found in this GitHub repository. To escalate privileges and disable defenses, threat actors can exploit legitimate software drivers, a list of which is available at loldrivers.io.
Unix/Linux. An extensive list of tools exploited by attackers can be found in the gtfobins repository on GitHub.
macOS. “Orchard” tools used in attacks are available at io.

It should be reiterated here that all the files listed in the links above are legitimate tools. They aren’t vulnerable per se, but can be used by an attacker who’s penetrated a system and gained sufficient privileges.

What’s stopping you from detecting LotL?

Even if an organization has a high level of information security maturity – with an expert team and advanced protective tools – in practice, defenders may be hampered in detecting LotL attacks due to the following reasons:

Non-adapted settings. Even advanced security tools need to be adapted to the specifics of the organization and the particularities of network segmentation, user-server interaction, and typical IT-system operating scenarios. Correlation rules need to be created and customized based on the available threat intelligence and known characteristics of the company. Sometimes defenders rely too heavily on IoC detection, and don’t pay enough attention to potentially dangerous behavioral signals. Sometimes InfoSec or IT services use broad exclusion rules and extensive allowlists that include many LOLBAS simply because they’re legitimate applications. All of the above significantly lowers the effectiveness of protection.
Inadequate logging. The standard level of logging in many systems doesn’t allow for the detection of malicious activity, storage of event parameters sufficient for incident analysis, or reliable differentiation between legitimate administrative actions and malicious ones.
Insufficient automation. Malicious actions in a heap of logs can only be detected after preliminary filtering and removal of background noise. The most effective filtering is telemetry from EDR, which collects relevant telemetry, increases flexibility in detecting attacker techniques, and reduces false positives. Without filtering and automated analysis, logs are useless. There are simply too many of them.
Isolation from IT. The above issues would be especially acute if IT and InfoSec services have little interaction: InfoSec is unfamiliar with IT work regulations, tool settings, and so on. In addition, if the teams don’t talk to each other, an investigation into suspicious activity can drag on for weeks or even months – during all of which time the threat actors would be further developing their attacks.

How to detect LotL attacks

There are many practical cybersecurity recommendations for detecting LotL attacks – none of them exhaustive. The most recent and detailed public guidance comes from cyber agencies in the US, UK, and Australia. But even there, the authors emphasize that they’re only providing best practice benchmarks.

The most practical, effective, and implementable detection tips are as follows:

Implement detailed event logging. Collect logs in a centralized repository that’s write-once and disallows modifications. This prevents attackers from deleting or changing logs. Centralization of logs is critical because it enables behavioral analysis, retrospective searches, and targeted threat hunting. It also often makes it possible to save logs for longer periods of time.
 
To be useful, logs must be comprehensive and verbose. They must log security events – including all commands in management consoles (shells), as well as system calls, PowerShell activity, WMI event traces, and so on. It’s worth reiterating that standard logging configurations rarely cover all necessary events. What’s more, in some cloud environments, the right level of logging is only available as part of costly service packages. When Microsoft 365 customers got burned this last year, Microsoft revised its policy.
 
For proper implementation of logging, SIEM (centralization, aggregation, and event analysis) and EDR (collection of necessary telemetry from hosts) are indispensable tools.
Identify and record typical, day-to-day activity of network devices, servers, applications, users, and administrators. To gather information about baseline behavior in a particular network, SIEM is recommended: all normal sequences of events, service relationships and the like are clear to see. Special attention should be paid to the analysis of “administrative” behavior, and the use of specific tools by privileged accounts – including system ones. Keep the number of administrative tools to a minimum, with detailed logging of their operation; use of other similar tools should be either blocked or set to trigger alerts. For administrator accounts, it’s important to analyze what time they are in use, what commands they run and in what sequence, what devices they interact with, and so on.
Use automated systems (such as machine learning models) to continuously analyze logs, match them against typical activity, and report anomalies to InfoSec. Ideally, implement user and entity behavior analytics (UEBA).
Continuously update settings to reduce background noise and adjust low-impact alerts or downgrade their priority.
 
You can fine-tune monitoring rules and alert triggers to better distinguish between routine administrative actions and potentially dangerous behavior. Avoid overly broad rules that will burden systems and analysts alike, such as “CommandLine=*”. Work with the IT team to reduce the variety of administration utilities used, their accessibility on unrelated systems, and the number of available protocols and types of accounts for logging in to corporate systems.

How to defend against LotL

The very nature of these attacks makes it almost impossible to prevent them completely. However, proper configuration of your network, endpoints, applications, and accounts can dramatically narrow the attack surface, speed up detection, and minimize the damage caused by intrusion attempts.

Review and implement “hardening” recommendations from vendors of the hardware and applications you use. The following should be considered as the minimum:

For Windows systems, apply Microsoft updates promptly.
For Linux systems, review permissions for key applications and daemons by following an industry guide – such as Red Hat Enterprise Linux Benchmarks.
For macOS devices, be aware that there are no generally accepted hardening recommendations, but there is a misconception that they’re secure out-of-the-box. In mixed networks, Windows devices are often more prevalent, such that IT and InfoSec tend to focus on Windows, overlooking threats and suspicious events on Apple devices. Besides the advice to regularly update macOS to the latest version and implement EDR/EPP, we recommend studying the macOS Security Compliance Project, which lets you generate InfoSec recommendations for specific macOS devices.
For organizations that actively use Microsoft 365 and Google Workspace cloud services, it’s vital to implement the minimum InfoSec recommendations from Microsoft and Google.
Critical IT assets, such as ADFS and ADCS for Microsoft-based IT systems, warrant special attention and in-depth analysis of possible hardening measures.
Widely apply universal hardening measures such as minimizing the number of running services, the principle of least privilege, and encryption and authentication of all network communications.

Make the allowlisting (aka default deny) approach standard. If implementing it across all applications and all computers is troublesome, try a phased approach. Popular LOLBAS that your team doesn’t use for work and your system processes don’t need can be blocked. The tools that actually are needed should only be available to administrators, only on relevant systems, and only for the duration of administrative tasks. All sessions that use such tools must be carefully logged and analyzed for anomalies.
 
Conduct an in-depth inventory of configurations, policies, and software installed on each host. If an application isn’t needed on a host, remove it: this will take it out of the toolkit of attackers and eliminate the headaches associated with updates and vulnerabilities. EDR solutions are ideal for this task.
Strengthen IT and OT network segmentation and monitoring at the internal network level. Besides isolating the OT network, you can move administrative machines with high privileges, important servers and the like to a separate subnet.

When implementing such restrictions, many organizations allowlist excessively broad IP ranges, for example, all addresses of a particular cloud provider. Even if this cloud hosts legitimate servers that the company server needs to communicate with, neighboring IPs could be leased by attackers. Therefore, it’s imperative to specify precise IP ranges and keep the allowlist as short as possible.

Network analysis tools should also be used to monitor traffic between segments, with a focus on unusual sessions and communications with more important network segments. Such analysis requires deep packet inspection (DPI).

To significantly simplify monitoring and to make attacks much harder, introduce privileged access workstations (PAWs) in your organization. High-risk administrative actions should be allowed on these and nowhere else. As part of the minimum program for Windows environments, operations with Active Directory servers should be allowed from PAWs only.

Implement authentication and authorization for all human-machine and machine-machine interactions regardless of their network location.
Implement a comprehensive approach to infrastructure protection based on detection and response tools (SIEM + EDR), building both awareness and team expertise (threat intelligence + cybersecurity training), and continuous hardening of the company’s overall InfoSec posture.

Kaspersky official blog – ​Read More

What commercial spyware is, and what different types there are | Kaspersky official blog

Commercial spyware has of late been making the headlines with increasing frequency. And we’re not just talking about media channels dedicated to IT or cybersecurity; reports on commercial spyware have been appearing regularly in mainstream media for some time now.

In this post, we discuss the existing commercial spyware packages, how they operate, what they’re capable of, and why they’re dangerous. And as always, we finish with advice on how to defend against them.

What is commercial spyware?

Let’s start with a definition. Commercial spyware is legal malware created by private companies and designed to conduct targeted surveillance and collect sensitive data from users’ devices. The standard tasks of commercial spyware include stealing messages, eavesdropping on calls, and tracking location.

To install commercial spyware on a victim’s device, attackers often use zero-day vulnerabilities, and in many cases — zero-click exploits, which make infection possible without requiring any action on the part of the victim.

Spyware always tries to be as inconspicuous as possible, for the longer the victim remains unaware of the infection, the more information attackers can gather. Moreover, commercial spyware often includes tools for removing traces of infection, so victims may not even suspect afterward that someone was monitoring them.

Although commercial spyware is developed by private companies, they typically sell it to various government organizations — primarily law enforcement and other security agencies.

As a result, commercial spyware is used, among other things, to monitor civilian activists, journalists, and other non-criminal individuals. In fact, that’s exactly why spyware programs regularly make the headlines.

1. Pegasus — NSO Group

Targeted OS: iOS, Android

Zero-day vulnerability exploitation: Apple iOS, Apple Safari, WhatsApp, Apple iMessage

Zero-click exploit use: yes

Country of origin: Israel

Alternative names: Chrysaor, DEV-0336, Night Tsunami

Now let’s talk about specific companies, starting with the most prominent player in the commercial spyware market — the notorious Israeli NSO Group, developer of the iOS spyware Pegasus, and its Android version Chrysaor. The early version of Pegasus, discovered in 2016, required the victim to click on a sent link, which opened a malicious page in a browser, which in turn triggered an automatic infection mechanism using the Trident exploit.

How Pegasus attacks were conducted in 2016. Source

The ability to infect iPhones using zero-click exploits quickly became a hallmark of Pegasus. For example, a few years ago, an attack on Apple smartphones exploited a vulnerability in WhatsApp voice calls activated with a series of malicious packets. The vulnerability, in turn, enabled remote code execution on the targeted device.

The FORCEDENTRY exploit, discovered by Citizen Lab in 2021 and thoroughly researched by the Google Project Zero team, is the most notorious. It was designed to attack the Apple iMessage system, enabling spyware to be launched on the victim’s iPhone after sending them a message containing a GIF file.

However, this file wasn’t an animated image at all but rather an infected PDF document in which a compression algorithm was used. When the victim’s smartphone attempted to preview the document, a vulnerability in the program responsible for handling this compression algorithm was triggered, leading to execution of a chain of exploits and, ultimately, infection of the device.

After this exploit was discovered, Apple patched the vulnerabilities. However, as it later turned out, NSO Group simply moved on to exploit vulnerabilities in other applications as if nothing had happened. In April 2023, the same Citizen Lab published research on the FINDMYPWN and PWNYOURHOME exploits. The former was linked to a vulnerability in Apple’s Find My app, while the latter targeted its HomeKit. However, the ultimate target for both of these exploits was the same: the iMessage messaging system.

Lockdown Mode messages about blocking PWNYOURHOME exploit attacks. Source

Finally, in September 2023, Citizen Lab released information about another exploit used by NSO Group: BLASTPASS. This exploit works similarly — also activating a vulnerability in iMessage — but this time related to the mechanism for sending Apple Wallet objects, such as event tickets, in messages.

Regardless of the specific attack vector, infection results in attackers gaining access to the victim’s messages, intercepting calls, stealing passwords, and tracking location. The geographical reach of this spyware is massive — and the corresponding section of the Pegasus Wikipedia entry occupies an impressive amount of space.

2. DevilsTongue, Sherlock — Candiru

Targeted OS: Windows, macOS, iOS, Android

Zero-day vulnerability exploitation: Microsoft Windows, Google Chrome

Zero-click exploit use: likely

Country of origin: Israel

Alternative names: SOURGUM, Caramel Tsunami, Saito Tech Ltd.

Another Israeli company that develops commercial spyware is Candiru, founded in 2014. In fact, this is only the first of the various names this cyber-espionage organization have used. Since they constantly change their moniker, it’s likely they’re working under a different one now. It’s known that Candiru is backed by several investors associated with NSO Group. However, unlike NSO Group, Candiru is much more secretive: the company has no website, its employees are forbidden to mention their employer on LinkedIn, and in the building where Candiru has its office, you won’t find any mention of it.

Official names changed by Candiru from 2014 to 2022. Source

Candiru’s activities have not been thoroughly studied yet — all the information we have is limited to leaked documents and a couple of incident investigations involving spyware developed by this company. For example, Microsoft’s investigation uncovered several zero-day vulnerabilities in the Windows operating system that Candiru exploited. There were also several zero-days in the Google Chrome browser, which Candiru probably exploited as well.

The company’s spyware is called DevilsTongue, and has multiple attack vectors — from hacking devices with physical access and using the man-in-the-middle method, to spreading malicious links and infected MS Office documents.

Capabilities of the DevilsTongue spyware developed by Candiru. Source

Candiru also offers a spy tool called Sherlock, which the researchers at Citizen Lab say could be a platform for zero-click attacks on various operating systems — Windows, iOS, and Android. Furthermore, there are reports that Candiru was developing spyware for attacks on macOS.

3. Alien, Predator — Cytrox / Intellexa

Targeted OS: Android, iOS

Zero-day vulnerability exploitation: Google Chrome, Google Android, Apple iOS

Zero-click exploit use: no (but something similar where the Mars complex is used)

Country of origin: North Macedonia / Cyprus

Alternative names: Helios, Balinese Ltd., Peterbald Ltd.

Alien is one of the two components of this spyware. It’s responsible for hacking the targeted device and installing the second part — necessary for setting up surveillance. This second part is called Predator — in homage to the movie.

The spyware was initially developed by Cytrox, founded in 2017. Its roots are in North Macedonia, with related subsidiary companies registered in both Israel and Hungary. Cytrox was later acquired by Cyprus-registered Intellexa, a company owned by Tal Dilian, who served 24 years in high-ranking positions in Israeli military intelligence.

The Alien/Predator spyware focuses on attacks on both the Android and iOS operating systems. According to last year’s Google Threat Analysis Group study, the developers of the Android version of Alien utilized several exploit chains — including four zero-day vulnerabilities in Google Chrome and one in Android.

Alien/Predator attacks started with messages to victims containing malicious links. Once clicked, these links directed victims to the attackers’ website, which exploited the vulnerabilities in the browser (Chrome) and OS (Android) to infect the device. It then immediately redirected the victim to a legitimate page to avoid suspicion.

Intellexa also offers the Mars spyware suite — part of which is installed on the victim’s mobile-operator’s side. Once installed, Mars waits for the targeted individual to visit an HTTP page, and when they do they use the man-in-the-middle method to redirect the victim to the infected site — at which point the process described in the previous paragraph triggers.

Infection by the Predator spyware using Mars occurs without any action on the part of the victim. This resembles a zero-click attack; however, in this case, additional equipment is used instead of vulnerabilities.

4. Subzero — DSIRF

Targeted OS: Windows

Zero-day vulnerability exploitation: Microsoft Windows, Adobe Reader

Zero-click exploit use: no

Country of origin: Austria

Alternative names: KNOTWEED, Denim Tsunami, MLS Machine Learning Solutions GmbH

The spyware Subzero, developed by the lengthily-named Austrian company DSR Decision Supporting Information Research Forensic GmbH (DSIRF), was first picked up by the German-speaking press back in 2021. However, it wasn’t until a year later that this spyware truly gained notoriety. In July 2022, the Microsoft Threat Intelligence team released a detailed study of spyware used by a group codenamed KNOTWEED (Denim Tsunami), which the researchers identified as DSIRF Subzero.

Slides from a DSIRF presentation detailing the capabilities of the spyware Subzero. Source

To compromise targeted systems, the Subzero malware exploited several zero-day vulnerabilities in both Windows and Adobe Reader. The attack vector typically involved sending the victim an email containing a malicious PDF file, which triggered a chain of exploits upon opening. As a result, bodiless spyware was launched on the victim’s device.

In the next stage, the spyware collected any passwords and other authentication credentials it could find in the infected system — from browsers, email clients, the Local Security Authority Subsystem Service (LSASS), and the Windows password manager. Presumably, these credentials were later used to gather information about the victim and set up further surveillance.

According to the researchers, the Subzero malware has been used to attack organizations in Europe and Central America since at least 2020. The researchers also noted that DSIRF not only sold spyware but also arranged for its employees to participate in the attacks.

In August 2023, it was announced that DSIRF would be shutting down. But it’s too early to rejoice just yet: it’s possible that cyber-espionage activities will be continued by DSIRF’s subsidiary — MLS, Machine Learning Solutions — which is believed to be the current owner of the Subzero spyware. By the way, the MLS website is still fully operational — unlike the DSIRF page, which was “under maintenance” at the time of writing.

5. Heliconia — Variston IT

Targeted OS: Windows, Linux

Zero-day vulnerability exploitation: Microsoft Defender, Google Chrome, Mozilla Firefox

Zero-click exploit use: no

Country of origin: Spain

Alternative names: none

Also in 2022, around the same time Microsoft published details about Subzero’s activities, Google presented its research analyzing another type of commercial spyware — Heliconia. The Google Threat Analysis Group (TAG) report described three components of this malware designed for attacks on computers running Windows or Linux.

The first part — called Heliconia Noise — exploits a vulnerability in the Google Chrome V8 JavaScript engine. Following its exploitation, Chrome’s sandbox is bypassed, and the spyware launches in the targeted system. Additionally, in the code of this part, a fragment was found mentioning Variston as the malware developer. The Google researchers believe it references the Spanish company Variston IT. This company specializes in providing information security services.

Researchers discovered a link to a company named Variston in the Heliconica code. Source

The second part of the spyware suite, which the Google researchers dubbed Heliconia Soft, exploits a vulnerability in the JavaScript engine embedded in the Windows antivirus, Microsoft Defender. This works as follows: first, the victim is sent a link to an infected PDF file containing malicious JavaScript code. This code triggers the Microsoft Defender vulnerability when the automatic scan of the downloaded PDF file starts. As a result of exploiting this vulnerability, Heliconia gains OS-level privileges and the ability to install spyware on the victim’s computer.

The third part is called Helicona Files. It exploits a vulnerability in the XSLT processor of the Mozilla Firefox browser to attack computers running Windows or Linux. Judging by this vulnerability, which affects Firefox versions 64 through 68, the spyware was developed quite some time ago and has been in use since at least 2018.

6. Reign — QuaDream

Targeted OS: iOS

Zero-day vulnerability exploitation: Apple iOS

Zero-click exploit use: yes

Country of origin: Israel / Cyprus

Alternative names: DEV-0196, Carmine Tsunami, InReach

QuaDream is another Israeli company that develops spyware called Reign. It was founded by former employees of NSO Group, and the spyware they’ve created bears a striking resemblance to Pegasus. For example, to infect iPhones with Reign spyware, they utilize a zero-click exploit similar to FORCEDENTRY, described above.

Citizen Lab researchers have dubbed this exploit ENDOFDAYS. Apparently, this exploit utilizes vulnerabilities in iCloud Calendar as the initial attack vector, enabling attackers to discreetly infect an iPhone by sending invisible malicious invitations to the calendar.

As for the spying capabilities of the iOS version of Reign, the list looks impressive:

searching files and databases
recording calls
listening through the microphone
taking photos with either front or rear cameras
stealing passwords
generating iCloud two-factor authentication one-time codes
tracking location
erasing traces of device infection

Capabilities of the sample iOS version of the QuaDream Reign spyware analyzed by Citizen Lab Source

According to some reports, QuaDream has also developed malware for attacking Android devices, but there’s no publicly available information about it. QuaDream’s penchant for secrecy is similar to that of Candiru. QuaDream also lacks a website, its employees are prohibited from discussing their work on social media, and the company’s office can’t be found on Google Maps.

Interestingly, QuaDream used an intermediary, the Cypriot company InReach, to sell its products. The relationship between these two companies is very complicated; at one point, they even went to court. In April 2023, shortly after publication of the Citizen Lab investigation into QuaDream, the company suddenly announced cessation of its operations; however, it’s not entirely clear yet whether this is a complete surrender or a tactical retreat.

How to defend against commercial spyware

Ensuring full protection against attacks using commercial spyware is generally challenging. However, you can at least make life harder for potential attackers. Follow these recommendations:

Regularly update the software on all your devices. First and foremost: operating systems, browsers, and messaging apps
Do not click on suspicious links — one visit to a site may be enough to infect your device
Use a VPN to mask your internet traffic — this will protect you from being redirected to a malicious site while browsing HTTP pages
Reboot regularly. Often, spyware can’t persist in an infected system indefinitely, so rebooting helps get rid of it
Install a reliable security solution on all your devices
And of course, read security expert Costin Raiu’s post for more tips on how to protect yourself from Pegasus and similar spyware

Kaspersky official blog – ​Read More

Transatlantic Cable podcast episode 339 | Kaspersky official blog

Episode 339 of the Transatlantic Cable podcast kicks off with news that several employees in TikTok were caught covertly spying on Forbes journalists. From there, the team talk about a new cooperation between governments to better tackle spyware and news that the FTC is looking at the upcoming Reddit IPO and AI training data.

To close out the podcast, the team discuss news that ‘at least 900’ websites built using Google’s FireBase cloud database may be leaking sensitive user data.

If you liked what you heard, please consider subscribing.

TikTok Spied On Forbes Journalists
Finland, Germany, Ireland, Japan, Poland, South Korea added to US-led spyware agreement
FTC investigating Reddit plan to sell user content for AI model training
900+ websites and expose millions of passwords via Firebase

Kaspersky official blog – ​Read More

What is SIM swapping, and how does it threaten business? | Kaspersky official blog

Today’s topic is SIM swap fraud, aka SIM swapping. This attack method is far from new but remains a live threat because of how effective it is. SIM swapping attacks pose a serious danger to business because they enable threat actors to gain access to corporate communications, accounts, and sensitive information like financial data.

What is SIM swapping?

SIM swapping is an attack method for hijacking a mobile phone number and transferring it to a device owned by the attackers. Put simply, said attackers go to a mobile telecoms operator’s office, somehow wangle a new SIM card with the number of a victim-to-be (see below for examples of how), insert it into their own phone, and thus gain access to the target’s communications.

It’s typically text messages that are of most interest to the attackers — specifically ones that contain one-time verification codes. Having gained access, they can then log in to accounts linked to the phone number and/or confirm transactions using the intercepted codes.

As for the SIM swapping process itself, there are various approaches by the bad guys. In some cases the criminals employ the services of an accomplice working for the mobile operator. In others, they deceive an employee using forged documents or social engineering.

The fundamental issue that makes SIM swapping possible is that in today’s world, SIM cards and cell phone numbers are not used solely for their designated purpose. They were not originally intended to serve as proof-of-identity which they’ve evolved into.

Now, one-time codes by text are a very common means of account security, which means that all other protective measures can be rendered null and void by a fraudster who smooth-talked a store employee into issuing a new SIM card with your number. Such a threat cannot be ignored.

For the targeted organization, a SIM swapping attack can hit the bottom line hard. Cybercriminal interest in cryptocurrency assets continues to grow as they can be hijacked relatively easily and, more importantly, quickly. However, this method can be applied in more sophisticated attacks, too.

U.S. Securities and Exchange Commission loses X account

For instance, here’s a very recent case. On January 9, 2024, the U.S. Securities and Exchange Commission (SEC) posted on X (Twitter) that it had approved a Bitcoin spot exchange-traded fund (ETF).

This Bitcoin-boosting event had long been in the pipeline, so the news didn’t strike anyone as implausible. Naturally, in the wake of the announcement, the Bitcoin price soared (by roughly 10% to $48,000).

Fake post from the hacked SEC account announcing the approval of a Bitcoin ETF. Source

However, the post was later deleted and replaced with a message that the SEC account had been compromised. The next day, X issued a statement saying that the compromise was due not to a breach of its systems, but to an unidentified individual who had obtained control over a phone number associated with the @SECGov account. Most likely, the jump in the Bitcoin price caused by the fake post meant the fraudster made a killing.

Then, toward the end of January, the SEC itself officially acknowledged that its X account had been hacked by SIM swappers. On top of that, it turned out that two-factor authentication (2FA), at the request of SEC staff, had been disabled by X support in July 2023 to resolve login issues. The issues duly resolved, they then simply forgot to turn 2FA back on — so until the January incident, the account was left without additional protection.

$400 million FTX crypto heist

It was only recently revealed that one of the largest crypto heists in history was carried out using SIM swapping. We’re talking about the theft of $400 million worth of assets from the FTX crypto exchange in the fall of 2022.

Initially, many suspected that FTX founder Sam Bankman-Fried himself was behind the heist. However, the ensuing investigation showed that he appeared to have nothing to do with it. Then came the indictment of a “SIM swapping group” headed by a certain Robert Powell.

Part of the indictment in the case of the $400 million FTX SIM-swap crypto heist. Source

The text of the indictment gave us the details of this heist, which, incidentally, was neither the gang’s first nor its last. The list of victims of its SIM-swap operations runs into the dozens. The indictment goes on to mention at least six more cases, in addition to FTX, involving the theft of large sums of money.

Here’s how the criminals operated: first, they selected a suitable victim and obtained their personal information. Next, one of the perpetrators forged documents in the victim’s name, but with the photo of another criminal — the one doing the actual SIM swap.

The latter criminal then paid a visit to the respective mobile operator’s office and got a replacement SIM card. Text messages with confirmation codes sent to the victim’s number were then intercepted and used to log in to the latter’s accounts and approve transactions for the transfer of assets to the gang. Interestingly, the very next day after the FTX heist, the group robbed a private individual in the exact same way to steal a modest-by-comparison $590,000.

How to guard against SIM swapping

As we see, in cases involving serious amounts of money, your SIM card and, accordingly, 2FA through one-time codes by text become the weak link. As the above examples show, SIM swapping attacks can be extremely effective; therefore, threat actors will doubtless continue to use them.

Here’s what to do to protect yourself:

Wherever possible, instead of a phone number, use alternative options to link your accounts.
Be sure to turn on notifications about account logins, pay close attention to them, and respond to suspicious logins as quickly as possible.
Again, where possible, avoid using 2FA with one-time codes by text.
For your 2FA needs, it’s better to use an authenticator app and a FIDO U2F hardware key — commonly called YubiKeys after the best-known brand.
Always use strong passwords to protect your accounts – this means unique, very long, and preferably randomly generated. To generate and store them, use a password manager.
And remember to protect those devices where passwords are stored and authenticator apps are installed.

Kaspersky official blog – ​Read More

How Wi-Fi WPA2 is hacked using PMKID interception | Kaspersky official blog

Being concerned about the security of your wireless network is not as paranoid as some may think it is. Many routers have a setting enabled by default that makes your WPA/WPA2-protected Wi-Fi network rather vulnerable. In this post, we’ll discuss one of the most effective methods of hacking wireless networks that exploits this setting, and how to protect against it.

The simplest and most effective attack on WPA/WPA2-PSK: PMKID interception

PMKID interception is the most effective, easy-to-execute, and completely undetectable method of attacking wireless networks protected by the WPA/WPA2 standards. In essence, this attack involves intercepting the encrypted Wi-Fi passwords that wireless routers broadcast constantly — even when no devices are connected to them. Having obtained the encrypted password, the attacker can use the brute-force method to decrypt it — and thereby connect to the Wi-Fi network.

This attack can also be carried out on a large scale using a technique called wardriving. Here, the attacker drives around a city scanning all available wireless networks and intercepting encrypted passwords that are broadcast by routers. Not much equipment is required for this — just a laptop, a long-range Wi-Fi adapter, and a powerful antenna.

The intercepted encrypted passwords can be cracked on the go. But an attacker may prefer to wait until they’re home and enter all the garnered passwords into a password-cracking tool on a high-performance computer (or rent computing power in the cloud). The effectiveness of this attack was recently demonstrated in Hanoi: a Vietnamese hacker scanned around 10,000 wireless networks and managed to decrypt the passwords for half of them.

This is all you need to hack 5000 wireless networks using PMKID interception. Source

How is it even possible to hack Wi-Fi using PMKID interception?

So why do wireless routers broadcast their Wi-Fi password all the time, albeit in encrypted form? Well, this is a basic function of the 802.11r standard, which is implemented on most routers and usually enabled by default. This standard enables fast roaming in Wi-Fi networks using multiple access points. To speed up the reconnection of the client device to new access points, they constantly broadcast their identifier — the very same PMKID.

This identifier is a derivative of the Pairwise Master Key (PMK). More precisely, it contains the result of an SHA-1 hash function calculation, whose source data includes the PMK key and some additional data. The PMK key itself, in turn, is the result of an SHA-1 hash function calculation of the Wi-Fi password.

In other words, the PMKID contains the wireless network password, hashed twice. In theory, the hashing process is irreversible, meaning it’s impossible to recover the original data from the resulting hashed value. Presumably, the creators of the 802.11r standard relied on this when devising the PMKID-based fast roaming mechanism.

However, hashed data can be brute-forced. This is made especially straightforward by the fact that people rarely use particularly strong passwords for wireless networks, often relying on fairly predictable combinations of characters instead. The creators of 802.11r obviously didn’t take this into account.

This problem was discovered a few years ago by the team behind one of the most popular password recovery utilities — in other words, a password-cracking tool — Hashcat. Since then, specialized tools have been developed specifically for cracking intercepted PMKIDs.

Successful extraction of the password “hashcat!” from the intercepted PMKID of a wireless network. Source

Thus, in practice, the attacker usually intercepts the PMKID containing the encrypted password, and then uses a dictionary attack — that is, they brute-force the most common passwords, which are collected in a database.

How to protect your wireless network from a PMKID attack

What can you do to prevent a PMKID interception attack on your wireless network? Fortunately, there are several protective measures that aren’t too difficult to implement:

Create a password for your wireless network that is as long and complex as possible. If a PMKID attacker intercepts the hashed password from your Wi-Fi, they still need to decrypt it afterward, but the more complex the password — the less likely the attackers are to succeed. Therefore, to protect against this attack, create the longest and most unguessable password possible for your wireless network.
Disable PMKID transmission in the router settings. Unfortunately, not all routers allow this, but it’s worth checking if yours has this setting. You can find it by searching for PMKID or 802.11r.
Switch to WPA3. If all your devices support this newer Wi-Fi security standard, it’s worth considering switching to it: WPA3 is generally much more secure than WPA2 and, importantly, isn’t susceptible to PMKID interception.
Set up a guest network. It can be tedious to have to frequently enter a strong password for the main network on new devices, so set up a guest network with a simpler password. By the way, it’s also a good idea to transfer potentially insecure things like IoT devices to the guest network.
Use the “Devices on My Network feature, which is available in our Kaspersky Plus and Kaspersky Premium This feature shows a list of devices on your network and alerts you if a new device connects to it.

For additional protection of transmitted data in case someone still manages to hack your Wi-Fi, use a VPN on all your devices to secure the internet connection — for example, our Kaspersky Secure Connection, which is also included in the Kaspersky Plus and Kaspersky Premium subscriptions.

Kaspersky official blog – ​Read More