WARNING WARNING ABOUT USE CCcam 2.30

cardsharing · 02-05-2012, 08:39 PM

CCCAM 2.3.0 is taking the backdoor crap even a step further.

The lowest scum of the earth, UVADI TEAM, have done it even better this time. Making sure sharing will die for sure if they keep this crap up.

Before I continue, I would urge people with BRAINS and PROGRAMMING SKILLS, to download IDA PRO (torrent) and decompile it for themselfs to find the remotely triggered backdoor.

How it works.

When you install CCcam 2.3.0 , nothing special is happening at first, and cccam will check for input activity on the pc or box to make sure nobody is watching. When it finds itself comfortably alone, it will start sending your ENTIRE CCCAM.CFG info to this IP 176.9.242.159 (a rented root server in germany).
Now I recompiled a version so I could trigger the backdoor myself, and TADA, some fucking ITALIAN dialup asswipe connected to the server I just set up , IP : 2.32.190.9. So traffic on my card started. THIS THEY CAN NOT HIDE in Cccam, it shows as a CONNECTED CLIENT from one of your clients in cccam.cfg where the dyndns has been removed (still lack of cccam, if dyndns is non-existing) the security feature doesn't work anymore and everybody can connect on that user.

The ...ure of CCcam is dead thanks to these low life asswipes , just after free sharing and making their own "spidernetwork" on your card.

BLOCK ALL CLIENTS that have 2.3.0 connected to your server as it will still read all connected clients from the server, trough the client

latest original CCcam 2.1.3 and 2.1.4 which are secure and don't have this backdoor code.

ps: AGAIN , if you don't want to take the warning for granted, decompile and look for yourself

!

2.1.3...2.1.4 only clients.

2.2.1 ..2.3.0 is big shit

Please tell these information to your peers

djah · 02-05-2012, 10:06 PM

FAKE

@admin
try to open the IP 176.9.242.159 in webbroswer

cardsharing · 02-06-2012, 02:14 PM

hehe, if web port is not open that does not mean that somebody does not listen your ccam server

Quote:

Originally Posted by djah

FAKE

@admin
try to open the IP 176.9.242.159 in webbroswer

dmaschine · 02-06-2012, 05:01 PM

Thk for info,

... and what do u mine about Cccam 2.0.11 ?

Regards

cardsharing · 02-07-2012, 07:14 AM

2.011. 2,11, 212 213 and 214 are oke

dmaschine · 02-07-2012, 01:38 PM

Thk

masrawysat · 02-07-2012, 09:00 PM

thx admin

samstar · 02-07-2012, 10:19 PM

Thanks for sharing your info

jamesmartin742010 · 02-10-2012, 08:52 PM

hey sticky how ya doing,, i am using 2.2.1 is that bad? what can i do about it , i'm worried.
i have 4 peers i'm sharing cards with, how do i know if they are taking advantage,,??
thanks for your time..

cardsharing · 02-10-2012, 09:55 PM

use 2.011. 2,11, 212 213 and 214

Quote:

Originally Posted by jamesmartin742010

hey sticky how ya doing,, i am using 2.2.1 is that bad? what can i do about it , i'm worried.
i have 4 peers i'm sharing cards with, how do i know if they are taking advantage,,??
thanks for your time..

02-05-2012, 08:39 PM	#1
cardsharing Administrator Join Date: Jan 2009 Posts: 1,914	WARNING WARNING ABOUT USE CCcam 2.30 CCCAM 2.3.0 is taking the backdoor crap even a step further. The lowest scum of the earth, UVADI TEAM, have done it even better this time. Making sure sharing will die for sure if they keep this crap up. Before I continue, I would urge people with BRAINS and PROGRAMMING SKILLS, to download IDA PRO (torrent) and decompile it for themselfs to find the remotely triggered backdoor. How it works. When you install CCcam 2.3.0 , nothing special is happening at first, and cccam will check for input activity on the pc or box to make sure nobody is watching. When it finds itself comfortably alone, it will start sending your ENTIRE CCCAM.CFG info to this IP 176.9.242.159 (a rented root server in germany). Now I recompiled a version so I could trigger the backdoor myself, and TADA, some fucking ITALIAN dialup asswipe connected to the server I just set up , IP : 2.32.190.9. So traffic on my card started. THIS THEY CAN NOT HIDE in Cccam, it shows as a CONNECTED CLIENT from one of your clients in cccam.cfg where the dyndns has been removed (still lack of cccam, if dyndns is non-existing) the security feature doesn't work anymore and everybody can connect on that user. The ...ure of CCcam is dead thanks to these low life asswipes , just after free sharing and making their own "spidernetwork" on your card. BLOCK ALL CLIENTS that have 2.3.0 connected to your server as it will still read all connected clients from the server, trough the client latest original CCcam 2.1.3 and 2.1.4 which are secure and don't have this backdoor code. ps: AGAIN , if you don't want to take the warning for granted, decompile and look for yourself ! 2.1.3...2.1.4 only clients. 2.2.1 ..2.3.0 is big shit Please tell these information to your peers

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

02-05-2012, 10:06 PM	#2
djah Junior Member Join Date: Jan 2011 Posts: 26	FAKE @admin try to open the IP 176.9.242.159 in webbroswer

02-06-2012, 05:01 PM	#4
dmaschine Junior Member Join Date: Sep 2011 Posts: 19	Thk for info, ... and what do u mine about Cccam 2.0.11 ? Regards

02-07-2012, 07:14 AM	#5
cardsharing Administrator Join Date: Jan 2009 Posts: 1,914	2.011. 2,11, 212 213 and 214 are oke

02-07-2012, 01:38 PM	#6
dmaschine Junior Member Join Date: Sep 2011 Posts: 19	Thk

02-07-2012, 09:00 PM	#7
masrawysat Member Join Date: May 2011 Posts: 45	thx admin

02-07-2012, 10:19 PM	#8
samstar Senior Member Join Date: Dec 2011 Posts: 139	Thanks for sharing your info

02-10-2012, 08:52 PM	#9
jamesmartin742010 Senior Member Join Date: Jul 2011 Posts: 106	hey sticky how ya doing,, i am using 2.2.1 is that bad? what can i do about it , i'm worried. i have 4 peers i'm sharing cards with, how do i know if they are taking advantage,,?? thanks for your time..

User Name		Remember Me?
Password