Topic: Bitcoin Bouny Hunter: Bitalo DDOS attacker discussion - page 4. (Read 11611 times)

Is it possible to get someone to look into this person:

Bernd Willmann; Rattinghauser Weg 6; 49324 Melle
Germany

Yes, that's me.

No, please, no!

I have all the information on DD4BC, someone responsible for the bounty pm me so we can discuss further on skype!

Martin,

Great information. Thanks!

Mike @ BITCOMSEC

Initial "small" ddos

i will have more logfiles from the follow ups

Direction IN
Internal 176.9.38.40
Threshold FlowsDiff 40 flows/s, Diff: 239 flows/s
Sum 71.841 flows/300s (239 flows/s), 71.881.000 packets/300s (239.603 packets/s), 2,738 GByte/300s (74 MBit/s)
External 211.153.8.169, 4 flows/300s (0 flows/s), 24.000 packets/300s (80 packets/s), 0,011 GByte/300s (0 MBit/s)
External 94.231.81.38, 3 flows/300s (0 flows/s), 3.000 packets/300s (10 packets/s), 0,001 GByte/300s (0 MBit/s)
External 173.74.75.83, 3 flows/300s (0 flows/s), 3.000 packets/300s (10 packets/s), 0,001 GByte/300s (0 MBit/s)
External 58.142.206.194, 2 flows/300s (0 flows/s), 3.000 packets/300s (10 packets/s), 0,000 GByte/300s (0 MBit/s)
External 67.55.209.73, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 177.47.16.130, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 78.97.94.244, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 219.124.114.1, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 199.58.240.1, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 196.23.6.234, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 58.210.9.222, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 219.159.39.58, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 61.97.9.100, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 194.185.38.14, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 205.171.93.37, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 120.83.5.152, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 72.13.143.84, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 186.219.240.68, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 58.240.213.254, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 207.240.120.138, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 111.195.28.4, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 183.232.148.17, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 112.214.75.254, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 89.137.112.222, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 46.36.35.180, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 111.12.150.169, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 4.26.50.58, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 37.252.196.14, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 78.84.22.172, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 183.232.112.18, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 12.89.10.34, 2 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 211.140.203.109, 1 flows/300s (0 flows/s), 3.000 packets/300s (10 packets/s), 0,001 GByte/300s (0 MBit/s)
External 213.192.9.248, 1 flows/300s (0 flows/s), 3.000 packets/300s (10 packets/s), 0,000 GByte/300s (0 MBit/s)
External 120.202.108.54, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 212.104.156.25, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 206.248.145.38, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 189.125.26.74, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 207.238.95.11, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 78.111.125.156, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 92.223.139.56, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 202.56.129.90, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 67.107.71.162, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,001 GByte/300s (0 MBit/s)
External 98.243.106.47, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 71.244.53.219, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 41.223.26.2, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 218.62.10.197, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 219.92.58.165, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 96.10.249.186, 1 flows/300s (0 flows/s), 2.000 packets/300s (6 packets/s), 0,000 GByte/300s (0 MBit/s)
External 98.214.231.148, 1 flows/300s (0 flows/s), 1.000 packets/300s (3 packets/s), 0,000 GByte/300s (0 MBit/s)
External 8.198.132.105, 1 flows/300s (0 flows/s), 1.000 packets/300s (3 packets/s), 0,000 GByte/300s (0 MBit/s)

Hi Roger,

My name is Mike and I'm with the BITCOMSEC (Bitcoin Community Secuity) Project. Our aim is to provide the community security services free of charge, and we're donation based. In the last year we've extensively audited exchanges, pools and merchants for security issues and provided the research to each of them respectively. Recently we've focused more on investigative research into these thieves:

Tracking down the CryptoRush.in hacker:
https://bitcomsec.true.io/bitcomsec/tracking-a-bitcoin-thief-cryptorush-hack/

Exposing and shutting down an elaborate Coinbase.com/Blockchain.info phishing network:
https://bitcomsec.true.io/bitcomsec/coinbase_com-and-blockchain_info-bitcoin-wallet-phishing-scam-exposed/

With that being said we are in the business of tracking down and exposing Bitcoin thieves to the community.

- Is there an archived copy of the extortion email + headers?

Thanks. Looking into this immediately.

Mike

Here is the full initial email communication. I will add more attack logfiles asap.                         
                                                                                                                                                                                                                                     
Delivered-To: [email protected]
Received: by 10.140.16.43 with SMTP id 40csp270558qga;
        Mon, 3 Nov 2014 06:33:55 -0800 (PST)
X-Received: by 10.60.68.108 with SMTP id v12mr602259oet.69.1415025235205;
        Mon, 03 Nov 2014 06:33:55 -0800 (PST)
Return-Path: <[email protected]>
Received: from SNT004-OMC1S8.hotmail.com (snt004-omc1s8.hotmail.com. [65.55.90.19])
        by mx.google.com with ESMTPS id 21si18495325oin.129.2014.11.03.06.33.53
        for
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
        Mon, 03 Nov 2014 06:33:55 -0800 (PST)
Received-SPF: pass (google.com: domain of [email protected] designates 65.55.90.19 as permitted sender) client-ip=65.55.90.19;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of [email protected] designates 65.55.90.19 as permitted sender) [email protected];
       dmarc=pass (p=NONE dis=NONE) header.from=outlook.com
Received: from SNT146-W55 ([65.55.90.9]) by SNT004-OMC1S8.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);
    Mon, 3 Nov 2014 06:33:53 -0800
X-TMN: [IyzY3qwIBGGm2XlnVY5tp8RicYKI1Pj8]
X-Originating-Email: [[email protected]]
Message-ID: <[email protected]>
Return-Path: [email protected]
Content-Type: multipart/alternative;
   boundary="_991179ca-6b3d-4765-8753-5bcd7337b00c_"
From: DD4BC TEAM <[email protected]>
To: Martin Albert <[email protected]>
CC: "[email protected]" <[email protected]>, "[email protected]"
   <[email protected]>, "[email protected]" <[email protected]>, "[email protected]"
   <[email protected]>, "[email protected]" <[email protected]>,
   "[email protected]" <[email protected]>, "[email protected]"
   <[email protected]>, "[email protected]" <[email protected]>,
   "[email protected]" <[email protected]>, "[email protected]" <[email protected]>,
   "[email protected]" <[email protected]>, "[email protected]"
   <[email protected]>, "[email protected]" <[email protected]>,
   "[email protected]" <[email protected]>, "[email protected]"
   <[email protected]>, "[email protected]" <[email protected]>,
   "[email protected]" <[email protected]>
Subject: RE: DDOS ATTACK!
Date: Mon, 3 Nov 2014 15:33:53 +0100
Importance: Normal
In-Reply-To: <[email protected]>
References:
 <[email protected]>,<[email protected]>,<[email protected]>,<[email protected]>,<[email protected]>,<[email protected]>,<[email protected]>,,<[email protected]>,<[email protected]>,<[email protected]>
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Nov 2014 14:33:53.0817 (UTC) FILETIME=[3157C890:01CFF773]

--_991179ca-6b3d-4765-8753-5bcd7337b00c_
Content-Type: text/plain; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Let me know if you are interested.=20

From: [email protected]
To: [email protected]
CC: [email protected]=3B [email protected]=3B [email protected]=3B mauro@bital=
o.com=3B [email protected]=3B [email protected]=3B [email protected]=3B lil=
[email protected]=3B [email protected]=3B [email protected]=3B [email protected]=
om=3B [email protected]=3B [email protected]=3B [email protected]=3B f=
[email protected]=3B [email protected]=3B [email protected]
Subject: RE: DDOS ATTACK!
Date: Sat=2C 1 Nov 2014 13:47:16 +0100

=0A=
=0A=
=0A=
To end this and because I'm in a good mood today=2C I will offer you a disc=
ounted price of 0.5 BTC=2C so we end this and I move further.

If yes: 17aLGgw8AwJdqiBtMMG1QtQJgNQQkiyEsp

If not=2C this is my last email to you and we will both be doing what we mu=
st...


From: [email protected]
To: [email protected]
Subject: RE: DDOS ATTACK!
Date: Sat=2C 1 Nov 2014 12:59:43 +0100

=0A=
=0A=
=0A=
Let me go back to important part:

In a first mail I have told you that I'm offering info how to properly prot=
ect your site. And that's true.

I'm not script kiddie and I know how this works=2C I can bypass =0A=
almost any protection (except Prolexic)=2C because I know every protection=
=0A=
 and their weaknesses - I'm regulary DDoS-ing sites behind CloudFlare and I=
ncapsula=2C Blacklotus=2C Staminus and OVH.

I know what I can't bypass and if I can't - nobody can.=20

When I say info how to properly setup=2C I mean how to do it for a good pri=
ce. Yes=2C you can always go for Prolexic and pay 10K per month.

From: [email protected]
To: [email protected]
Subject: RE: DDOS ATTACK!
Date: Sat=2C 1 Nov 2014 12:39:33 +0100

=0A=
=0A=
=0A=
OMG=2C no! That hurts!

What am I going to do if I lose my Outlook account... LOL.=20


You know what's funny?

This morning I dreamed that somebody=2C somehow=2C found  my real name and =
published it in a press release... And there was my name all over the Inter=
net... When I woke up=2C I laughed.

Because it's possible only in a dream.

DDoS attacks are impossible to trace back to origin. You can try over email=
 logins like you are doing=2C but there are two things:

- Microsoft will not give you my IPs just like that. You need to report me =
to your local police in Finland=2C then THEY must ask for my login directly=
 from Microsoft or through FBI.

- Once they (and IF=2C because they probably won't care) get my login IPs=
=2C they will point to TOR...


And third=2C probably most important=2C you are not helping yourself doing =
this.


Date: Sat=2C 1 Nov 2014 12:58:11 +0200
Subject: Fwd: DDOS ATTACK!
From: [email protected]
To: [email protected]=3B [email protected]

Dear outlook team=2C
we want to report a criminal abuse of your mail system (see mail below) and=
 would like to request all login data from the user so that we can forward =
these to the local police authorities
---------- Forwarded message ----------
From: DD4BC TEAM <[email protected]>
Date: Sat=2C Nov 1=2C 2014 at 4:57 AM
Subject: DDOS ATTACK!
To: "[email protected]" <[email protected]>=2C "[email protected]" talo.com>=2C "[email protected]" <[email protected]>=2C "[email protected]" [email protected]>=2C "[email protected]" <[email protected]>=2C "michael@bital=
o.com" <[email protected]>=2C "[email protected]" <[email protected]>=2C "ma=
[email protected]" <[email protected]>=2C "[email protected]" m>=2C "[email protected]" <[email protected]>=2C "[email protected]" talo.com>=2C "[email protected]" <[email protected]>=2C "trevin@bital=
o.com" <[email protected]>=2C "[email protected]" <[email protected]>=
=2C "[email protected]" <[email protected]>=2C "[email protected]" [email protected]>=2C "[email protected]" <[email protected]>=2C "martin.alb=
[email protected]" <[email protected]>


=0A=
=0A=
=0A=

=0A=
=0A=
=0A=
=0A=
=0A=

HelloYour site is extremely vulnerable to ddos attacks.I want to offer you =
info how to properly setup your protection=2C so that you can't be ddosed!M=
y price is 1 Bitcoin only.Right now I will star small (very small) attack w=
hich will not crash your server=2C but you should notice it in logs. Just c=
heck it.I want to offer you  info on how I did it and what you have to do t=
o prevent it. If interested pay me 1 BTC to 17aLGgw8AwJdqiBtMMG1QtQJgNQQkiy=
EspThank you.    =20
=0A=
                                            =0A=

                                                                                        =

--_991179ca-6b3d-4765-8753-5bcd7337b00c_
Content-Type: text/html; charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable

Let me know if you are intereste=
d.

---

From: [email protected]
To: mart=
[email protected]
CC: [email protected]=3B [email protected]=3B [email protected]=
om=3B [email protected]=3B [email protected]=3B [email protected]=3B maciej@=
bitalo.com=3B [email protected]=3B [email protected]=3B [email protected]=3B s=
[email protected]=3B [email protected]=3B [email protected]=3B michael=
[email protected]=3B [email protected]=3B [email protected]=3B martin.albert@gm=
x.net
Subject: RE: DDOS ATTACK!
Date: Sat=2C 1 Nov 2014 13:47:16 +010=
0

=0A=
=0A=
=0A=

To end this and because I'm in a good mood today=2C I will=
 offer you a discounted price of 0.5 BTC=2C so we end this and I move furth=
er.

If yes: 17aLGgw8AwJdqiBtMMG1QtQJgNQQkiyEsp

If not=2C this=
 is my last email to you and we will both be doing what we must...
 style=3D"color:rgb(51=2C51=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetic=
a=2CArial=2Csans-serif=3Bfont-size:14px=3Bfont-style:normal=3Bfont-variant:=
normal=3Bfont-weight:normal=3Bletter-spacing:normal=3Bline-height:21.875px=
=3Btext-align:start=3Btext-indent:0px=3Btext-transform:none=3Bwhite-space:n=
ormal=3Bword-spacing:0px=3Bdisplay:inline !important=3Bbackground-color:rgb=
(250=2C250=2C250)=3B">

---

From: =
[email protected]
To: [email protected]
Subject: RE: DDOS ATTACK!
=
Date: Sat=2C 1 Nov 2014 12:59:43 +0100

=0A=
=0A=
=0A=

Let me go back to important part:

In a first mail I=
 have told you that I'm offering info how to properly protect your site. An=
d that's true.

I'm not script kiddie and I know how this works=2C I =
can bypass =0A=
almost any protection (except Prolexic)=2C because I know every protection=
=0A=
 and their weaknesses - I'm regulary DDoS-ing sites behind CloudFlare and I=
ncapsula=2C Blacklotus=2C Staminus and OVH.

I know what I can't bypa=
ss and if I can't - nobody can.

When I say info how to properly set=
up=2C I mean how to do it for a good price. Yes=2C you can always go for Pr=
olexic and pay 10K per month.

---

From: =
[email protected]
To: [email protected]
Subject: RE: DDOS ATTACK!
=
Date: Sat=2C 1 Nov 2014 12:39:33 +0100

=0A=
=0A=
=0A=

OMG=2C no! That hurts!

What am I going to do if I l=
ose my Outlook account... LOL.


You know what's funny?

Th=
is morning I dreamed that somebody=2C somehow=2C found =3B my real name=
 and published it in a press release... And there was my name all over the =
Internet... When I woke up=2C I laughed.

Because it's possible only =
in a dream.

DDoS attacks are impossible to trace back to origin. =
You can try over email logins like you are doing=2C but there are two thing=
s:

- Microsoft will not give you my IPs just like that. You need to =
report me to your local police in Finland=2C then THEY must ask for my logi=
n directly from Microsoft or through FBI.

- Once they (and IF=2C bec=
ause they probably won't care) get my login IPs=2C they will point to TOR..=
.


And third=2C probably most important=2C you are not helping yo=
urself doing this.

---

Date: Sat=
=2C 1 Nov 2014 12:58:11 +0200
Subject: Fwd: DDOS ATTACK!
From: martin=
@bitalo.com
To: [email protected]=3B [email protected]

=3D"ltr">

Dear outlook team=2C

we want to repo=
rt a criminal abuse of your mail system (see mail below) and would like to =
request all login data from the user so that we can forward these to the lo=
cal police authorities

---------- Fo=
rwarded message ----------
From: DD4BC =
TEAM <=3Bdd4bc=
@outlook.com>=3B
Date: Sat=2C Nov 1=2C 2014 at 4:57 AM
S=
ubject: DDOS ATTACK!
To: "martin@bi=
talo.com" <=3B[email protected]<=
/a>>=3B=2C "[email protected]" <=
=3B[email protected]>=3B=2C "ef=3D"mailto:[email protected]">[email protected]" <=3Bo:[email protected]">[email protected]>=3B=2C "bitalo.com">[email protected]" <=3B>[email protected]>=3B=2C "mauro@b=
italo.com" <=3B[email protected]a>>=3B=2C "[email protected]" =
<=3B[email protected]>=3B=2C=
 "[email protected]" <=3B=3D"mailto:[email protected]">[email protected]>=3B=2C "to:[email protected]">[email protected]" <=3B@bitalo.com">[email protected]>=3B=2C ".com">[email protected]" <=3Blilia=
@bitalo.com>=3B=2C "felix@bitalo.=
com" <=3B[email protected]>=
=3B=2C "[email protected]" <=3Bhref=3D"mailto:[email protected]">[email protected]>=3B=2C "mailto:[email protected]">[email protected]" <=3Blto:[email protected]">[email protected]>=3B=2C "lto:[email protected]">[email protected]" <=3B[email protected]">[email protected]>=3B=2C "italo.com">[email protected]" <=3Blo.com">[email protected]>=3B=2C "o.com">[email protected]" <=3B">[email protected]>=3B=2C "fa=
[email protected]" <=3Bfabiob@bita=
lo.com>=3B=2C "[email protected]=
om" <=3B[email protected]&=
gt=3B=2C "[email protected]>" <=3B[email protected]=
>=3B


=0A=
=0A=
=0A=

=0A=
=0A=
=0A=

=0A=
=0A=

Helvetica Neue'=2CHelvetica=2CArial=2Csans-serif=3Bfont-size:14px=3Bfont-st=
yle:normal=3Bfont-variant:normal=3Bfont-weight:normal=3Bletter-spacing:norm=
al=3Bline-height:21.875px=3Btext-align:start=3Btext-indent:0px=3Btext-trans=
form:none=3Bwhite-space:normal=3Bword-spacing:0px=3Bdisplay:inline !importa=
nt=3Bbackground-color:rgb(250=2C250=2C250)=3B">Hello
or:rgb(51=2C51=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=2Cs=
ans-serif=3Bfont-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3Bfont=
-weight:normal=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-align:=
start=3Btext-indent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bword-s=
pacing:0px=3Bbackground-color:rgb(250=2C250=2C250)=3B">
gb(51=2C51=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=2Csans-=
serif=3Bfont-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3Bfont-wei=
ght:normal=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-align:star=
t=3Btext-indent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bword-spaci=
ng:0px=3Bbackground-color:rgb(250=2C250=2C250)=3B">(51=2C51=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=2Csans-se=
rif=3Bfont-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3Bfont-weigh=
t:normal=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-align:start=
=3Btext-indent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bword-spacin=
g:0px=3Bdisplay:inline !important=3Bbackground-color:rgb(250=2C250=2C250)=
=3B">Your site is extremely vulnerable to ddos attacks.
color:rgb(51=2C51=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=
=2Csans-serif=3Bfont-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3B=
font-weight:normal=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-al=
ign:start=3Btext-indent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bwo=
rd-spacing:0px=3Bbackground-color:rgb(250=2C250=2C250)=3B">
or:rgb(51=2C51=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=2Cs=
ans-serif=3Bfont-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3Bfont=
-weight:normal=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-align:=
start=3Btext-indent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bword-s=
pacing:0px=3Bbackground-color:rgb(250=2C250=2C250)=3B">:rgb(51=2C51=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=2Csan=
s-serif=3Bfont-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3Bfont-w=
eight:normal=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-align:st=
art=3Btext-indent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bword-spa=
cing:0px=3Bdisplay:inline !important=3Bbackground-color:rgb(250=2C250=2C250=
)=3B">I want to offer you info how to properly setup your protection=2C so =
that you can't be ddosed!
-family:'Helvetica Neue'=2CHelvetica=2CArial=2Csans-serif=3Bfont-size:14px=
=3Bfont-style:normal=3Bfont-variant:normal=3Bfont-weight:normal=3Bletter-sp=
acing:normal=3Bline-height:21.875px=3Btext-align:start=3Btext-indent:0px=3B=
text-transform:none=3Bwhite-space:normal=3Bword-spacing:0px=3Bbackground-co=
lor:rgb(250=2C250=2C250)=3B">family:'Helvetica Neue'=2CHelvetica=2CArial=2Csans-serif=3Bfont-size:14px=
=3Bfont-style:normal=3Bfont-variant:normal=3Bfont-weight:normal=3Bletter-sp=
acing:normal=3Bline-height:21.875px=3Btext-align:start=3Btext-indent:0px=3B=
text-transform:none=3Bwhite-space:normal=3Bword-spacing:0px=3Bdisplay:inlin=
e !important=3Bbackground-color:rgb(250=2C250=2C250)=3B">My price is 1 Bitc=
oin only.
ca Neue'=2CHelvetica=2CArial=2Csans-serif=3Bfont-size:14px=3Bfont-style:nor=
mal=3Bfont-variant:normal=3Bfont-weight:normal=3Bletter-spacing:normal=3Bli=
ne-height:21.875px=3Btext-align:start=3Btext-indent:0px=3Btext-transform:no=
ne=3Bwhite-space:normal=3Bword-spacing:0px=3Bbackground-color:rgb(250=2C250=
=2C250)=3B">
eue'=2CHelvetica=2CArial=2Csans-serif=3Bfont-size:14px=3Bfont-style:normal=
=3Bfont-variant:normal=3Bfont-weight:normal=3Bletter-spacing:normal=3Bline-=
height:21.875px=3Btext-align:start=3Btext-indent:0px=3Btext-transform:none=
=3Bwhite-space:normal=3Bword-spacing:0px=3Bbackground-color:rgb(250=2C250=
=2C250)=3B"> Neue'=2CHelvetica=2CArial=2Csans-serif=3Bfont-size:14px=3Bfont-style:norma=
l=3Bfont-variant:normal=3Bfont-weight:normal=3Bletter-spacing:normal=3Bline=
-height:21.875px=3Btext-align:start=3Btext-indent:0px=3Btext-transform:none=
=3Bwhite-space:normal=3Bword-spacing:0px=3Bdisplay:inline !important=3Bback=
ground-color:rgb(250=2C250=2C250)=3B">Right now I will star small (very sma=
ll) attack which will not crash your server=2C but you should notice it in =
logs. Just check it.
ly:'Helvetica Neue'=2CHelvetica=2CArial=2Csans-serif=3Bfont-size:14px=3Bfon=
t-style:normal=3Bfont-variant:normal=3Bfont-weight:normal=3Bletter-spacing:=
normal=3Bline-height:21.875px=3Btext-align:start=3Btext-indent:0px=3Btext-t=
ransform:none=3Bwhite-space:normal=3Bword-spacing:0px=3Bbackground-color:rg=
b(250=2C250=2C250)=3B">
Helvetica Neue'=2CHelvetica=2CArial=2Csans-serif=3Bfont-size:14px=3Bfont-st=
yle:normal=3Bfont-variant:normal=3Bfont-weight:normal=3Bletter-spacing:norm=
al=3Bline-height:21.875px=3Btext-align:start=3Btext-indent:0px=3Btext-trans=
form:none=3Bwhite-space:normal=3Bword-spacing:0px=3Bbackground-color:rgb(25=
0=2C250=2C250)=3B">lvetica Neue'=2CHelvetica=2CArial=2Csans-serif=3Bfont-size:14px=3Bfont-styl=
e:normal=3Bfont-variant:normal=3Bfont-weight:normal=3Bletter-spacing:normal=
=3Bline-height:21.875px=3Btext-align:start=3Btext-indent:0px=3Btext-transfo=
rm:none=3Bwhite-space:normal=3Bword-spacing:0px=3Bdisplay:inline !important=
=3Bbackground-color:rgb(250=2C250=2C250)=3B">I want to offer you =3B in=
fo on how I did it and what you have to do to prevent it. If interested pay=
 me 1 BTC to 17aLGgw8AwJdqiBtMMG1QtQJgNQQkiyEsp
b(51=2C51=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=2Csans-s=
erif=3Bfont-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3Bfont-weig=
ht:normal=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-align:start=
=3Btext-indent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bword-spacin=
g:0px=3Bbackground-color:rgb(250=2C250=2C250)=3B">
=2C51=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=2Csans-serif=
=3Bfont-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3Bfont-weight:n=
ormal=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-align:start=3Bt=
ext-indent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bword-spacing:0p=
x=3Bbackground-color:rgb(250=2C250=2C250)=3B">
1=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=2Csans-serif=3Bf=
ont-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3Bfont-weight:norma=
l=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-align:start=3Btext-=
indent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bword-spacing:0px=3B=
background-color:rgb(250=2C250=2C250)=3B">=2C51)=3Bfont-family:'Helvetica Neue'=2CHelvetica=2CArial=2Csans-serif=3Bfo=
nt-size:14px=3Bfont-style:normal=3Bfont-variant:normal=3Bfont-weight:normal=
=3Bletter-spacing:normal=3Bline-height:21.875px=3Btext-align:start=3Btext-i=
ndent:0px=3Btext-transform:none=3Bwhite-space:normal=3Bword-spacing:0px=3Bd=
isplay:inline !important=3Bbackground-color:rgb(250=2C250=2C250)=3B">Thank =
you.  =3B  =3B

=0A=
                     

                    

=0A=

                    

                    

          =
          

                    

=

--_991179ca-6b3d-4765-8753-5bcd7337b00c_--

Please use this thread for discussion of the Bitalo DDOS attacker case specifically: http://bitcoinbountyhunter.com/bitalo.html

For general discussion about BitcoinBountyHunter.com,  please use: https://bitcointalksearch.org/topic/bitcoinbountyhuntercom-bitcoin-bounties-to-catch-the-crooks-784520