Darn, interesting article and that would have been the icing on the CakeGroup-IB didn’t say ... how attackers managed to plant the Raspberry Pi
As do the hackers, probably. Maybe they’re trying to pay them off.All these hackers and we still have student loans SMH
The researchers then used a forensic tool to analyze the communications.
Modern lexicon is “allow list” and “deny list” not “whitelist” and “blacklist”I was always under the impression that banks whitelisted all connections on some networks as SOP. Apparently I'm wrong or they were able to somehow add the Pi to the whitelist.
It's not hard to do, and since you know your topology it should be even easier.
Because it had access to the monitoring server, it probably was installed on the data center side, not down next to an ATM/branch. That narrows the suspects down considerably.
One funny thing is that it just takes one bribe to get that in. I mean, if someone paid you $500k to plug in a random device in a restricted area would you do it? What about a million? Two?
I just want to know what they are doing running an FTP server in 2025 (the service listening on port 21 in the screenshot)
If they can do these attacks then nation states can do far worse. It’s better to have a minor nuisance than major vulnerability go undetected. But yes, ultimately they should be paid for these exploits through legitimate means.You have to admire the sheer skill and tenacity these groups demonstrate, really wish they would find a different creative outlet though.
Don't assume that port 21 means FTP.I just want to know what they are doing running an FTP server in 2025 (the service listening on port 21 in the screenshot)
802.1x is how you put a stop to this.Well, on the one hand dealing with 802.1X is kind of a pain in the ass; but on the other hand just hoping that I'm not worth the trouble of someone actually motivated is hard to justify.
That convenience store ATM uses a cell modem, but most bank operated ones don't. This was an unauthorized device using a 4G modem to bridge over their firewall.Why the hell do ATMs use 4G instead of a direct cable connection?
I just want to know what they are doing running an FTP server in 2025 (the service listening on port 21 in the screenshot)
That's just someone on the 10th floor with a fancy laptop and this shiny new thing called wifi.Ran into a similar attempt early 2000’s.
Giant company I worked for leased a 15 story tower to other tenants, including a bank on the 1st floor.
We had IDFs on each floor above 6 (we occupied 6-15). Also had our switches shut down any port with an unknown MAC appearance.
Kept having ports go dark on 10th floor. Drove over, open the supposedly secure door on 10, and found a LinkSys router plugged into my switch. Someone had a keycard, and was apparently moving the router to a green port every few days.
Yikes….
Not unusual if anyone has watched the show Mr. Robot. Reality imitating fiction, imitating reality?“One of the most unusual elements of this case was the attacker’s use of physical access to install a Raspberry Pi device[.]”
Make one wonder if it's someone with inside knowledge of bank security.The researchers with security firm Group-IB said the “unprecedented tactic allowed the attackers to bypass perimeter defenses entirely.” The hackers combined the physical intrusion with remote access malware that used another novel technique to conceal itself, even from sophisticated forensic tools.
Then again, I understand cash-strapped North Korea is always looking for ways to get money.The group behind the attack is tracked in the industry under the name UNC2891. The financially motivated threat group has been active since at least 2017 in targeting the infrastructures of banks.
At an org I used to work for, heard from a manager that one IT admin got canned when the network admins found out he had put his own server in a network room to mine Bitcoin. This was happening around the same timeframe as your problem, so not as expensive as it would be now, but still a significant siphoning of company resources, not to mention possible security issues.Ran into a similar attempt early 2000’s.
Giant company I worked for leased a 15 story tower to other tenants, including a bank on the 1st floor.
We had IDFs on each floor above 6 (we occupied 6-15). Also had our switches shut down any port with an unknown MAC appearance.
Kept having ports go dark on 10th floor. Drove over, open the supposedly secure door on 10, and found a LinkSys router plugged into my switch. Someone had a keycard, and was apparently moving the router to a green port every few days.
Yikes….
Modern acceptance of older-than-dirt concepts of black and white dualism as being connected in any way to arbitrary racial labels is a deeply unhealthy pathology on about a million levels and very, very sad.Modern lexicon is “allow list” and “deny list” not “whitelist” and “blacklist”
802.1x is how you put a stop to this.
People have trouble with 802.1x because certificates are equivalent to the Black Speech of Mordor, and because banks will be required to change the authentication credentials on a quasi-regular basis (device certificate renewal with EAP-TLS or EAP-TTLS, or a new password annually if you use PEAP-MSCHAPv2 or PEAP-PAP or something similar)
[Master/Slave] has entered the chat.Modern acceptance of older-than-dirt concepts of black and white dualism as being connected in any way to arbitrary racial labels is a deeply unhealthy pathology on about a million levels and very, very sad.
It's not as if that's a new concept. Just look at how Ford treated the Pinto issues in the 70s - lawyers were deemed cheaper than engineering a fix.I had some infrastructure dealings with financial institutions long ago and the number one thing I took away from it was that their interest in security vanished when the cost of implementing security exceeded the average amount lost to theft.
...Pretty much. Wasn't it a fairly major plot point that Sauron made a subtle error in specifying name constraints when issuing one of the nine rings of men, because qualified subordination is just simple like that, and ended up allowing Éowyn to completely invalidate the security assurances that were supposed to be inherent to the Witch-king of Angmar?
That's what always makes me jumpy about dealing with the things. The cryptic failures if you do something wrong are one thing; but the cryptic successes by people who aren't you if you do something wrong are just plain hard on the nerves.
That's pretty much every business.I had some infrastructure dealings with financial institutions long ago and the number one thing I took away from it was that their interest in security vanished when the cost of implementing security exceeded the average amount lost to theft.
The lesson, kids, is if you're going to take a bribe from scumbags to plant their hacks, get the money up front.I was always under the impression that banks whitelisted all connections on some networks as SOP. Apparently I'm wrong or they were able to somehow add the Pi to the whitelist.
It's not hard to do, and since you know your topology it should be even easier.
Because it had access to the monitoring server, it probably was installed on the data center side, not down next to an ATM/branch. That narrows the suspects down considerably.
One funny thing is that it just takes one bribe to get that in. I mean, if someone paid you $500k to plug in a random device in a restricted area would you do it? What about a million? Two?
convenience store ATM
Luckily the upcoming 45 day public cert lifetime limit is going to force vendors to make ACME support robust so that will reduce the friction in rolling out 802.1x. We're still running into some issues with the tools our cert vendor supplies but they're getting more robust basically in real time, I expect in a few years it'll work pretty smoothly.802.1x is how you put a stop to this.
People have trouble with 802.1x because certificates are equivalent to the Black Speech of Mordor, and because banks will be required to change the authentication credentials on a quasi-regular basis (device certificate renewal with EAP-TLS or EAP-TTLS, or a new password annually if you use PEAP-MSCHAPv2 or PEAP-PAP or something similar)