Re: [TSCM-L] {2633} Re: Use of cell phone as a Listening device

From: kondrak <kon..._at_phreaker.net>
Date: Wed, 14 May 2008 00:47:33 -0400

>From - Sat Mar 02 00:57:17 2024
Received: by 10.90.88.17 with SMTP id l17mr4552068agb.14.1210546072052;
        Sun, 11 May 2008 15:47:52 -0700 (PDT)
Return-Path: <dave..._at_hotmail.com>
Received: from bay0-omc1-s3.bay0.hotmail.com (bay0-omc1-s3.bay0.hotmail.com [65.54.246.75])
        by mx.google.com with ESMTP id 7si8177965yxg.1.2008.05.11.15.47.51;
        Sun, 11 May 2008 15:47:52 -0700 (PDT)
Received-SPF: pass (google.com: domain of dave..._at_hotmail.com designates 65.54.246.75 as permitted sender) client-ip=65.54.246.75;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of dave..._at_hotmail.com designates 65.54.246.75 as permitted sender) smtp.mail=dave..._at_hotmail.com
Received: from hotmail.com ([64.4.61.82]) by bay0-omc1-s3.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);
         Sun, 11 May 2008 15:47:51 -0700
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
         Sun, 11 May 2008 15:47:51 -0700
Message-ID: <BAY102-DAV106AB329F6851A453D6532DACD0_at_phx.gbl>
Received: from 216.48.162.184 by BAY102-DAV10.phx.gbl with DAV;
        Sun, 11 May 2008 22:47:50 +0000
X-Originating-IP: [216.48.162.184]
X-Originating-Email: [dave..._at_hotmail.com]
X-Sender: dave..._at_hotmail.com
Reply-To: "Dave Milk" <dave..._at_hotmail.com>
From: "Dave Milk" <dave..._at_hotmail.com>
To: <TSCM-..._at_googlegroups.com>
References: <a43bc5e9-4ab4-4d0b-a92f-ca99fcef99d9_at_b1g2000hsg.googlegroups.com> <4826AE2F.4070007_at_phreaker.net>
Subject: Re: [TSCM-L] {2629} Re: Use of cell phone as a Listening device
Date: Sun, 11 May 2008 18:47:46 -0400
Mime-Version: 1.0
Content-Type: multipart/alternative;
        boundary="----=_NextPart_000_00E0_01C8B397.80E0F840"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-OriginalArrivalTime: 11 May 2008 22:47:51.0226 (UTC) FILETIME=[0AD741A0:01C8B3B9]
Return-Path: dave..._at_hotmail.com

------=_NextPart_000_00E0_01C8B397.80E0F840
Content-Type: text/plain; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable

yes it can, a blue tooth enabled enabled Phone can be switched on by a bad =
guy with a fairly simple capture device, it can even be made to call number=
s with theout the owners knowledgte or consent, Hope that helps some
Dave=20
  From: kondrak=20
  To: TSCM-..._at_googlegroups.com=20
  Sent: Sunday, May 11, 2008 4:28 AM
  Subject: [TSCM-L] {2629} Re: Use of cell phone as a Listening device


  Yes, and yes.
  BUT, and its a big BUT, they have to load software onto the phone, and th=
at can only be done from the switch, so it has to be an inside job with the=
 carrier's consent,

  ka3..._at_netscape.net wrote:=20
I had a question from a client about cell phones in a meeting used as
a listening device.

I told the client that yes a cell phone could be used as a =93bug=94. But
as to the clients question I am not sure.

Here is the question.

=93Can a cell phone be used as a =93bug=94 without the owner=92s knowledge?
Can someone call a cell phone get it not to ring, auto answers without
the owner=92s knowledge and listen to a meeting?=94

I told the client I had not heard of it but anything could be possible
with a digital device.

What are the group=92s thoughts?



 =20
 =20


------=_NextPart_000_00E0_01C8B397.80E0F840
Content-Type: text/html; charset=Windows-1252
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3Dtext/html;charset=3Dwindows-1252>
<META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>yes it can, a blue tooth enabled enabled P=
hone can=20
be switched on by a bad guy with a fairly simple capture device, it can eve=
n be=20
made to call numbers with theout the owners knowledgte or consent, Hope tha=
t=20
helps some</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Dave</FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LE=
FT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>Fro=
m:</B>=20
  <A title=3Dkon..._at_phreaker.net href=3D"mailto:kon..._at_phreaker.net">kondra=
k</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A title=3DTSCM-..._at_googlegrou=
ps.com=20
  href=3D"mailto:TSCM-..._at_googlegroups.com">TSCM-..._at_googlegroups.com</A>=
=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, May 11, 2008 4:28 AM=
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [TSCM-L] {2629} Re: Use o=
f cell=20
  phone as a Listening device</DIV>
  <DIV><BR></DIV>Yes, and yes.<BR><B>BUT, and its a big BUT</B>, they have =
to=20
  load software onto the phone, and that can only be done from the switch, =
so it=20
  has to be an inside job with the carrier's consent,<BR><BR><A=20
  class=3Dmoz-txt-link-abbreviated=20
  href=3D"mailto:ka3..._at_netscape.net">ka3..._at_netscape.net</A> wrote:=20
  <BLOCKQUOTE=20
  cite=3Dmid:a43bc5e9-4ab4-4d..._at_b1g2000hsg.googlegroups.com=20
  type=3D"cite"><PRE wrap=3D"">I had a question from a client about cell ph=
ones in a meeting used as
a listening device.

I told the client that yes a cell phone could be used as a =93bug=94. But
as to the clients question I am not sure.

Here is the question.

=93Can a cell phone be used as a =93bug=94 without the owner=92s knowledge?
Can someone call a cell phone get it not to ring, auto answers without
the owner=92s knowledge and listen to a meeting?=94

I told the client I had not heard of it but anything could be possible
with a digital device.

What are the group=92s thoughts?



  </PRE></BLOCKQUOTE><BR>
------=_NextPart_000_00E0_01C8B397.80E0F840--
Received on Sat Mar 02 2024 - 00:57:17 CST

This archive was generated by hypermail 2.3.0 : Sat Mar 02 2024 - 01:11:44 CST