[Fire_Star]

Hello,

i would pay anyone $10, if u could help me resolve my issue (reputed members only). I already have a crypter and its working fine. But the problem is avast behaviour shield is detecting my crypted stub i guess at the point when the server is meant to connect to the client.

I have tried NJRat and Quasar and i checked records for my DNS and IP everything is clean. i dont know wats the problem.

I have literally tried everything (Different settings, etc) but no luck and i am to my wits end.

If anyone could help me over TV i would really appreciate it.

My Skype is fire_star15

Thanx and Regards.

[kinginondexx]

Ur crypters broke then it's not fud

[Cthulhu1]

Ur crypters broke then it's not fud

just because a crypter isnt FUD doesnt mean its broken. lol

[Fire_Star]

The Crypter is FUD, I have done some tests and come to the conclusion that Avast Behavior Shield is detecting it a point of injection (i guess so), i have tried self injection and injecting into svchost, vbc, etc still the detection occurs and i have tried it with Native Rats as well.

[VisualSoft]

The Crypter is FUD, I have done some tests and come to the conclusion that Avast Behavior Shield is detecting it a point of injection (i guess so), i have tried self injection and injecting into svchost, vbc, etc still the detection occurs and i have tried it with Native Rats as well.

This is called Runtime Detection.

[Fire_Star]

This is called Runtime Detection.

Its showing clean on run4me.net

anyway to bypass it?

[VisualSoft]

Its showing clean on run4me.net

anyway to bypass it?

thats only scantime result and not runtime.
When a Crypted file gets detected after running it, Its called Runtime detection.
You need to change your crypter is only Option.

[Fire_Star]

Issue has been resolved. Please Delete this Thread.