Godlike Productions - Discussion Forum
Users Online Now: 1,737 (Who's On?)Visitors Today: 502,779
Pageviews Today: 828,350Threads Today: 284Posts Today: 5,332
09:53 AM


Back to Forum
Back to Forum
Back to Thread
Back to Thread
REPORT COPYRIGHT VIOLATION IN REPLY
Message Subject Yea, so my son hacked my pacemaker...
Poster Handle zulu
Post Content
Sadly, this can be easily done by someone who knows what they are doing in terms of knowing about SDR stuff.

All someone needs to do is get a list of the providers who manufacture these devices (who offers them aka company), do some research to get FCC details (ton of info about the device > frequency it operates > etc.. I probably said a little too much.

It is quite scary.
 Quoting: zulu 76646999


That is pretty much what he was telling me. I didnt understand it but it didnt make me happy. Do you know if they are working at a solution for this?
 Quoting: Whiskey Tango Foxtrot


Negative. No one is currently working on a solution as far as I know. I honestly wouldn't even know how they would even come up with a solution.

This can go deeper situation wise. Your home device that plugs into your telephone line communicates with your pacemaker. (If you have one of those) The device sends the data to the clinic for the review of the data. (Not sure what the procedure is) If someone wanted, they could technically sit there and sniff the frequency looking for data to RECORD and then retransmit the data. Technically, not only can they trigger your pacemaker (if they truly know what their doing) they can also troll and flood the data to your clinic, your clinic will think there is something more wrong (your health) or will think there is malfunctions in which will lead to them wanting to conduct surgery on you to so call fix the device. There is just a ton of possibilities, but I'm sure no one would even want to take the time to go through all of that unless they were really going after someone or just plainly sick in the head.
 
Please verify you're human:




Reason for copyright violation:







GLP