Topic: **ANN** DLUX ** DeluxCoin ** Scrypt ** PoW/PoS ** Biometric Encryption ** (Read 1997 times)
October 28, 2015, 03:39:30 AM
Somehow these viruses are usually not active on my station i don't know thus that it is because of the antivirus or they are having some dependencies
October 28, 2015, 02:41:04 AM
one of the ones...
October 28, 2015, 02:35:35 AM
Is this the one with virus in wallet?
October 28, 2015, 12:24:38 AM
This dev is a hero, doing what is needed in altcoins - diluting the market with scammy shit so people stop caring about new launches totally and the entire concept dies a much needed death.
Good work dev keep it up!
Good work dev keep it up!
October 27, 2015, 09:29:22 PM
meh..
October 27, 2015, 08:50:07 PM
BCT talk needs to take the next step and ban newbie accounts from creating threads. It's not a fail safe measure, but at least these devs will have to try harder before releasing RATs and scams on the community. May be more trouble for them than it is worth.
That's a very good idea. 
in 10 days i'm try save u money 3 times ! 3 fucking times... Demonic,LunarCoin,DeluxCoinThis motherfuckers do not stop The fight will be lost if the admin will not do anything...
edit: ok approx sent to Kaspersky Lab malware, Comodo, ESET 32 when they checked it will go to update antivirus signatures he wiped control over your computers;)
ps.google translator power: D
October 27, 2015, 08:43:47 PM
BCT talk needs to take the next step and ban newbie accounts from creating threads. It's not a fail safe measure, but at least these devs will have to try harder before releasing RATs and scams on the community. May be more trouble for them than it is worth.
Couldn't agree more, just wasting our time, and stealing other newbies BTC.
The next obstacle is that people sell their accounts, some BTC in escrow as collateral?
October 27, 2015, 08:27:04 PM
BCT talk needs to take the next step and ban newbie accounts from creating threads. It's not a fail safe measure, but at least these devs will have to try harder before releasing RATs and scams on the community. May be more trouble for them than it is worth.
That's a very good idea. 
October 27, 2015, 08:19:12 PM
BCT talk needs to take the next step and ban newbie accounts from creating threads. It's not a fail safe measure, but at least these devs will have to try harder before releasing RATs and scams on the community. May be more trouble for them than it is worth.
October 27, 2015, 07:46:51 PM
Thank you oc and 5m4ru1. For this and all your service to crypto.
October 27, 2015, 07:37:54 PM
October 27, 2015, 07:16:31 PM
He's probably already preparing the next one.... at least my scripts are working and we have a few users with hex editor skills
October 27, 2015, 07:15:24 PM
Glad I dodged a bullet this time.
October 27, 2015, 07:14:51 PM
bu bitche !
oh well, thanks for the tip
ill just do a total change and you wont be able to find it at all 
btw i have some dox about you taken from your own PC LOL
saved only in my head and clean windows virtualbox u have so many ehhh ;/ October 27, 2015, 07:05:31 PM
oh well, thanks for the tip
ill just do a total change and you wont be able to find it at all btw i have some dox about you taken from your own PC LOL
October 27, 2015, 07:01:58 PM
bu bitche !
Aaaahhh so I was right, good cath 5m4ru ! Damn.. When will this ever stop.. Are you really making that much money with all those Trojans all the time ?
Guys, I'm closing the pool, sorry for the wasted time !
October 27, 2015, 06:58:48 PM
bu bitche !
https://i.imgur.com/EM3KxNJ.png
https://i.imgur.com/EM3KxNJ.png
October 27, 2015, 06:48:25 PM
I don't want to FUD, but a certain IP in the nodelist triggered one of my alarm-scripts:
After some digging a similar IP was used for/with Tianhe and Dracula Coin, both contained a Trojan/Virus so YMMV but be warned:
https://bitcointalksearch.org/topic/m.12417463
https://bitcointalksearch.org/topic/m.11690668
However - this can just be a bad coincidence.. Just make sure you've got the wallet sandboxed - I did the same on my side.
Code:
{
"addr" : "31.215.21.13:12063",
"services" : "00000001",
"lastsend" : 1445988269,
"lastrecv" : 1445988269,
"bytessent" : 9102,
"bytesrecv" : 2252,
"conntime" : 1445987907,
"pingtime" : 0.28261200,
"version" : 60015,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 434,
"banscore" : 0,
"syncnode" : false
}
"addr" : "31.215.21.13:12063",
"services" : "00000001",
"lastsend" : 1445988269,
"lastrecv" : 1445988269,
"bytessent" : 9102,
"bytesrecv" : 2252,
"conntime" : 1445987907,
"pingtime" : 0.28261200,
"version" : 60015,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 434,
"banscore" : 0,
"syncnode" : false
}
After some digging a similar IP was used for/with Tianhe and Dracula Coin, both contained a Trojan/Virus so YMMV but be warned:
https://bitcointalksearch.org/topic/m.12417463
https://bitcointalksearch.org/topic/m.11690668
However - this can just be a bad coincidence.. Just make sure you've got the wallet sandboxed - I did the same on my side.
i'm not sure what the point is, but i cant see this IP on those tinahe and dracula coins threads ?
EDIT: also this IP is NOT the seed node!
You can see a similar IP on those threads (starting with 31.215...)
Like I said before, could also just be a bad coincidence..
Well it might be a miner from that IP range , however its always best to scan/sandbox wallets before use.
October 27, 2015, 06:44:10 PM
I don't want to FUD, but a certain IP in the nodelist triggered one of my alarm-scripts:
After some digging a similar IP was used for/with Tianhe and Dracula Coin, both contained a Trojan/Virus so YMMV but be warned:
https://bitcointalksearch.org/topic/m.12417463
https://bitcointalksearch.org/topic/m.11690668
However - this can just be a bad coincidence.. Just make sure you've got the wallet sandboxed - I did the same on my side.
Code:
{
"addr" : "31.215.21.13:12063",
"services" : "00000001",
"lastsend" : 1445988269,
"lastrecv" : 1445988269,
"bytessent" : 9102,
"bytesrecv" : 2252,
"conntime" : 1445987907,
"pingtime" : 0.28261200,
"version" : 60015,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 434,
"banscore" : 0,
"syncnode" : false
}
"addr" : "31.215.21.13:12063",
"services" : "00000001",
"lastsend" : 1445988269,
"lastrecv" : 1445988269,
"bytessent" : 9102,
"bytesrecv" : 2252,
"conntime" : 1445987907,
"pingtime" : 0.28261200,
"version" : 60015,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 434,
"banscore" : 0,
"syncnode" : false
}
After some digging a similar IP was used for/with Tianhe and Dracula Coin, both contained a Trojan/Virus so YMMV but be warned:
https://bitcointalksearch.org/topic/m.12417463
https://bitcointalksearch.org/topic/m.11690668
However - this can just be a bad coincidence.. Just make sure you've got the wallet sandboxed - I did the same on my side.
i'm not sure what the point is, but i cant see this IP on those tinahe and dracula coins threads ?
EDIT: also this IP is NOT the seed node!
You can see a similar IP on those threads (starting with 31.215...)
Like I said before, could also just be a bad coincidence..
October 27, 2015, 06:38:24 PM
I don't want to FUD, but a certain IP in the nodelist triggered one of my alarm-scripts:
After some digging a similar IP was used for/with Tianhe and Dracula Coin, both contained a Trojan/Virus so YMMV but be warned:
https://bitcointalksearch.org/topic/m.12417463
https://bitcointalksearch.org/topic/m.11690668
However - this can just be a bad coincidence.. Just make sure you've got the wallet sandboxed - I did the same on my side.
Code:
{
"addr" : "31.215.21.13:12063",
"services" : "00000001",
"lastsend" : 1445988269,
"lastrecv" : 1445988269,
"bytessent" : 9102,
"bytesrecv" : 2252,
"conntime" : 1445987907,
"pingtime" : 0.28261200,
"version" : 60015,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 434,
"banscore" : 0,
"syncnode" : false
}
"addr" : "31.215.21.13:12063",
"services" : "00000001",
"lastsend" : 1445988269,
"lastrecv" : 1445988269,
"bytessent" : 9102,
"bytesrecv" : 2252,
"conntime" : 1445987907,
"pingtime" : 0.28261200,
"version" : 60015,
"subver" : "/Satoshi:1.0.0/",
"inbound" : true,
"startingheight" : 434,
"banscore" : 0,
"syncnode" : false
}
After some digging a similar IP was used for/with Tianhe and Dracula Coin, both contained a Trojan/Virus so YMMV but be warned:
https://bitcointalksearch.org/topic/m.12417463
https://bitcointalksearch.org/topic/m.11690668
However - this can just be a bad coincidence.. Just make sure you've got the wallet sandboxed - I did the same on my side.
i'm not sure what the point is, but i cant see this IP on those tinahe and dracula coins threads ?
EDIT: also this IP is NOT the seed node!
Jump to: