Woke up to like 100 tags on this iPhone implant. Which is found in this video here: https://t.co/9khbpmUQEH

I don’t speak Russian, but I do have a first grade language fluency in hardware. So lets take a look!
Thread 1/n

So a lot of people have correctly identified it as this GPS & Wifi based location tracker with microphone.
A very common type of device, similar to what is found in those extremely suspicious looking USB cables: https://t.co/uBhi7tRhiW

2/n
The headers are designed to attach a specific USB connector that fits a micro SD card in the tip.
3/n
A repurposed board is very “hobby implant” but... we see the SIM card was removed, which would make this a wifi-only implant. Yet an external GSM antenna is attached and only the ground for power? Cant see the other side though...
4/n
Upon closer inspection, they removed the SIM slot housing and soldered a SIM card directly to the pads. That gains a little more space.

Thanks @dcuthbert

5/n https://t.co/Sq9X6yByPV
You can see an antenna in the upper right. Right on a metal shield which will hurt the range.
There is normally not a convenient place for an implant, but they swapped the battery for a smaller one.
6/n
This feels like a proof of concept done for the video, or a fairly low grade implant done with a tiny budget. It could be done way smaller by not repurposing an existing thumb drive module.

7/n
For many adversaries that want location & mic, I suspect they generally don’t need a hardware implant. But there are always exceptions. That’s not really my area though.
8/n
Looks like @Requiem_fr has a nice visual comparison showing the battery reduction for clearing space.

This is a technique I have also used in power supplies when needing a little extra space for... activities 😈

9/n https://t.co/KjgfREmhZt
If true, this seems almost like it was intended to be found. The work is really primitive for gov work, not to mention the other ways they can pull location & mic.

10/n https://t.co/AwNiFpIE2V
The “shrink the power source” approach was what I used for this project:

11/n https://t.co/gz3cuKC6jb
Here is a previously unpublished picture of the internals. It’s all cannibalized COTS hardware.
This was before I got into hardware design. Not very good, but enough for a proof of concept.

12/n
One plausible idea: this only needed to last long enough to see where the phone went before it was torn open. That would give some valuable info.

13/n https://t.co/M77sGjOmcW
Anyway. I’m just going off a few pictures as I haven’t had the time to properly research it. For all I know, this was created as a stand-in for video demo purposes.
14/n

More from Tech

I think about this a lot, both in IT and civil infrastructure. It looks so trivial to “fix” from the outside. In fact, it is incredibly draining to do the entirely crushing work of real policy changes internally. It’s harder than drafting a blank page of how the world should be.


I’m at a sort of career crisis point. In my job before, three people could contain the entire complexity of a nation-wide company’s IT infrastructure in their head.

Once you move above that mark, it becomes exponentially, far and away beyond anything I dreamed, more difficult.

And I look at candidates and know-everything’s who think it’s all so easy. Or, people who think we could burn it down with no losses and start over.

God I wish I lived in that world of triviality. In moments, I find myself regretting leaving that place of self-directed autonomy.

For ten years I knew I could build something and see results that same day. Now I’m adjusting to building something in my mind in one day, and it taking a year to do the due-diligence and edge cases and documentation and familiarization and roll-out.

That’s the hard work. It’s not technical. It’s not becoming a rockstar to peers.
These people look at me and just see another self-important idiot in Security who thinks they understand the system others live. Who thinks “bad” designs were made for no reason.
Who wasn’t there.
One of the best decisions I made during a very turbulent 2020 was to leave conventional coding behind and embrace the #nocode movement. @bubble made this a reality. Although my own journey thus far is premature, I’ve learned a lot so here’s a power thread on....


‘How I created @buildcamp sales funnel landing page in under 2hours’.

Preview here 👇

https://t.co/s9P5JodSHe

Power thread here 👇

1. Started with a vanilla bubble app ensuring that all styles and UI elements were removed. Created a new page called funnel and set the page size to 960px as this allows the page to render proportionately on both web and mobile when hitting responsive breakpoints.


2. Began dropping elements onto the page to ‘find the style’. These had to be closely aligned to our @buildcamp branding so included text, buttons and groups - nothing too heavy. Played around with a few fonts, colors and gradients and thus pinned down the following style guide.


3. Started to map out sections using groups as my ‘containers’ to hold the relevant information and imagery needed to pad out the sales pitch. At this point, they were merely blocks of color #ff6600 with reduced opacity set to 5% to ease page flair.

You May Also Like