good lord. I pulled a microSD card out of a Raspi inside an IoT product and it appears they had some developer use a raspi to develop/test some software, and then they just yanked the SD card out of that machine and duped it on to all of their deployed products.

it's got .bash_history of the development process! there's git checkouts of private repos! WHY WOULD YOU DO THIS?

I've also been able to de-stealth a "stealth startup" on linked in.
because this has commits from different users, and I can just look up on linkedin what stealth-startup all those people work/worked at and then look at the name on the IoT box I'm holding

also, you punks are writing python 2 code in 2021? come on, who does that?

I mean, I do all the time, but I'm a known retrocomputerist. I run Windows 95 and MS-DOS regularly. of course I'm using a wildly outdated programming language. I'm not making a product I sell to customers!

oh cool you can pull the GPS history of a truck from azure without any login, you just need to know the device ID.
this might be UPS trucks. I should probably not query any of these GPS histories

also they're spamming 9 lines to syslog every minute.

this is a microsd card in a raspi, guys! you are going to fry your fucking card by running out of write cycles. That's not a good idea in any raspi application, especially not an IoT one

oh sweet jesus they logged into slack from this machine('s image)

I have their chrome profile, with history and cookies and shit!

this is deeply embarrassing. I have lists of their duckduckgo and google searches for the programming problems they were having building this product.

no programmer should ever have that personal shame shared with the world. let alone included on every microSD card your company ships!

oh sweet jesus

they automatically scp up some logs to a server somewhere. Did they set up keys so that authorized devices could log in automatically without passwords?

NOPE THEY USED SSHPASS

I have a file here with multiple lines like:

sudo sshpass -p PASSWORDHERE scp /path/system/network.log USERNAME@IPADDRESS:/home/manufacturing/

well I'm putting this away so I don't accidentally hack them.

this is one of the many reasons I'm not a security researcher.

it's a target rich environment.

Also I'm a reverse engineer. There's no reverse engineering here!
I unscrewed the box, pulled out the raspi, pulled the SD card out, put it in my laptop, and it automounted. I then looked at some files while making a disgusted face.

That's not reverse engineering! That's just lookin'

Also this isn't the only opsec failure they've made but if I say what the other one is, you might be able to figure out what company this is. And if you can do that, they can too, and they might get mad at me
I just noticed this is how they heatsinked that raspberry pi I yanked the SD card out of.
@foone what did this iot product do?
@Viss @foone per earlier post, tracks trucks

@ian It's a cheap truck-tracking trick.

@Viss @foone

@foone i love that the left heatsink is also not the appropriate size at all
@ada @foone Likely because it was intended for that IC on the right (RAM iirc?) rather than the EMI shield it's sitting on
@foone well, I don't want to say it, but, if I read your posts, I might come to the conclusion that this device was not carefully designed nor built at all!
@foone
Pretty sure they already can with the info you've just written down if they want.

Pretty sure they also don't want, because it would be embarrassing to the extreme for them to come forward after what you just wrote down 😂
@wouter Well, some companies ironically value their reputation so much and fear such blunders becoming widely known to the point that they would cause a Streisand-Effect when trying to bury it.
@foone oh my god, this is the real life example of the old joke "it works on my machine" "ok box it up and send it to the data center"
@foone I want off Mr. IoT's Wild Ride
@foone please tell me at least they're out of business?

@bshah that matters little. The cloned iot devices are still in use in the wild.

@foone

@foone

As always, you are my hero.

This is jaw-dropping bad.

Play some old Lode Runner on an Apple ][ emulator for brain bleach.

Nice find.

#infosec

See if they have a bug bounty program. They won't, given these kinds of findings, but clearly they should.

@foone As they say: The S in IoT is for Security …
@foone I'm imagining the dev said "hey, it works!" and five minutes later found himself laid off. Five minutes after that, they were cloning this card. 🤦‍♀️🙅‍♀️🙎‍♀️
@foone The choice paralysis alone is insane!
@foone this thread just slowly became worse and worse as I was reading it 

@Polychrome @foone

Yeah. Foone had great timing. Like watching a good stand up comedian, but for security sadness.

@Two9A Your thread has been unrolled! You can view the full conversation at: https://threadtree.xyz/112820532329423282
@Two9A Your thread has been unrolled! You can view the full conversation at: https://threadtree.xyz/112820532329423282
@Two9A Your thread has been unrolled! You can view the full conversation at: https://threadtree.xyz/112820532329423282
@foone You know, I never get bored of your tech adventures. Stay awesome. 💜
@foone i don't really understand completely what is explained but i read the thread as an excellent investigation and thriller movue. Thank you.
🍿

@ciredutempsEsme @foone well, it's as much an investigation as visiting a flat and immediately discovering the remains of a meth-lab operation, with unattended unstable chemicals.

I suspect the team for that was one dev that hacked it together and cut all the corners until they got a smooth circle.

@tshirtman @ciredutempsEsme @foone sounds like they laid off their one man dev team the minute they had a working prototype, no?

@theothersimo @ciredutempsEsme @foone well, or features were always too high prio for quality to happen.

I've been a one man team shipping devices with custom software to places, and yeah, times was always too short to think about small things like security (though for that business that wasn't really a concern, the worst that could happen was people stealing our code and running with it).

@foone @ciredutempsEsme ask, and we shall try to answer. Any question you have, someone else has the same question but is afraid to ask.
@BenAveling @foone
It would be too many questions and I guess i would fond the answer looking on the internet si i won't bother you but a big thank you for thé proposition
@foone @ciredutempsEsme you can probably find answers to specific questions on the internet, but if you need help putting it all together, feel free to ask.
@foone oh i think i would die instantly
@foone do you need an OVE?
@cadey a what?
@foone diet CVE
@cadey nah. I didn't get this device legitimately, so I can't really report any security holes in it.

@foone that’s why we need protection for people who report this stuff.

You may want to talk to folks from @CCC to find the right process to get this off the road before it causes bodily harm.

@cadey

@foone you could go anonymous through a disclosure intermediary like ZDI…
@aardvark They already posted publicly about it though... better to not have "someone else" suddenly report that right now. (But I hope that some people get tipped off by this, shouldn't be too hard to find what it is by the clues)
@the_moep elliptically tooting on Mastodon isn’t really disclosure to the vendor (no matter how entertaining).
@foone i mean it's very bad from a security perspective, but it's very convenient from a hacking perspective.
@dysfun @foone This. A closed, locked down surveillance device is worse than an open one.