Earlier quoted context omitted.
We did get a hand written statement from him and the original evidence (hardware) is still untouched and locked away. In his statement he wrote that the pi logged to the SD card but there was no data on the SD card (well not on the data partition) and I'm pretty sure that was a lie and it just logged to Balena. But even though we could never decipher what the nodejs program actually did (because it was so heavily obf…
how hard can you obfuscate nodejs? I'm pretty sure if you drop the code in some infosec channels they will happily take the challenge and tell you what it does ;)
The curious case of the Raspberry Pi in the network closet (2019)
151–160 of 269 posts
Re: The curious case of the Raspberry Pi in the network closet (2019)
#152Earlier quoted context omitted.
We did get a hand written statement from him and the original evidence (hardware) is still untouched and locked away. In his statement he wrote that the pi logged to the SD card but there was no data on the SD card (well not on the data partition) and I'm pretty sure that was a lie and it just logged to Balena. But even though we could never decipher what the nodejs program actually did (because it was so heavily obf…
Any plans to release to code? I would love to take a look.
Re: The curious case of the Raspberry Pi in the network closet (2019)
#153Earlier quoted context omitted.
We did get a hand written statement from him and the original evidence (hardware) is still untouched and locked away. In his statement he wrote that the pi logged to the SD card but there was no data on the SD card (well not on the data partition) and I'm pretty sure that was a lie and it just logged to Balena. But even though we could never decipher what the nodejs program actually did (because it was so heavily obf…
>he was tracking the movement data of the boss to avoid him whenever possible. Wow, imagine hating your boss so much you go to so much creative and illegal lengths (that can backfire against you) to track him, instead of using same skills legally to finding a better job. I just don't get, something doesn't feel right about this being the true reason. To me it looks more like he wanted a covert backdoor in the company…
Re: The curious case of the Raspberry Pi in the network closet (2019)
#154Earlier quoted context omitted.
This, truly, is the thing to worry about: if it happened here, it likely happened at other companies. Turning a blind eye is a blank check to do it again.
File that under "not this companies problem"
Re: The curious case of the Raspberry Pi in the network closet (2019)
#155Re: The curious case of the Raspberry Pi in the network closet (2019)
#156Author of the article here. Since I first published this blog post I was getting messages from people asking how it ended. Sadly it's pretty anticlimactic as the owner of the place had a meeting with the guy who put the Pi there (without me as he didn't want the Pi-dropper to feel ambushed) and in the end decided not to escalate it to legal and just basically told him to pack his things and get out. So no legal after…
Re: The curious case of the Raspberry Pi in the network closet (2019)
#157Earlier quoted context omitted.
how hard can you obfuscate nodejs? I'm pretty sure if you drop the code in some infosec channels they will happily take the challenge and tell you what it does ;)
An easier solution might be to look at the packets the nodejs program is sending over the network (if you can configure a MITM)
Re: The curious case of the Raspberry Pi in the network closet (2019)
#158Author of the article here. Since I first published this blog post I was getting messages from people asking how it ended. Sadly it's pretty anticlimactic as the owner of the place had a meeting with the guy who put the Pi there (without me as he didn't want the Pi-dropper to feel ambushed) and in the end decided not to escalate it to legal and just basically told him to pack his things and get out. So no legal after…
> So no legal after play and just a slap on the wrist The problem with this is you have no idea what harm the guy actually may have caused; nor what other RPis he may have set up around the company or around town. Next time he may be more careful with his username, set up the disk to be encrypted w/ a network key, &c, making future exploits more difficult to track down.
Re: The curious case of the Raspberry Pi in the network closet (2019)
#159Re: The curious case of the Raspberry Pi in the network closet (2019)
#160Reminder (from a security guy): what the author did is risky. If you are really worried about a compromised server or a suspicious device call security consultant / forensic experts.
What are the potential risks around what he did?
- Losing access to forensic data by not capturing the contents of the device RAM. Pretty common.
- Becoming witness of a crime and getting personally targeted by some criminal organization in retaliation. This one should be obvious.
- Wasting the opportunity to keep the device on to monitor the activity of the intruder