Skip to content

Commit 2a4d52d

Browse files
author
bytecode77
committed
FUD.md
1 parent 70e2d9c commit 2a4d52d

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

FUD.md

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Is PEunion FUD?
2+
3+
The sole purpose of a crypter is to decrease the detection rate of an executable, ideally to the point where it is not detected by any AV.
4+
5+
**So, why is PEunion not FUD?**
6+
7+
PEunion *was* FUD as of September 2021. However, any crypter will remain FUD only for a certain period of time. This is especially the case for a crypter that is public & free.
8+
9+
**Is it possible to fix this and make PEunion FUD?**
10+
11+
It is possible to address detection issues and fix them. However, keeping PEunion FUD long term is a job that would require several hours of work each day.
12+
13+
This is time that I am just not going to invest. Developers who provide a crypter that is guaranteed to be FUD will typically sell it and put in the time to continually make proper modifications.
14+
15+
**What is the purpose PEunion then?**
16+
17+
PEunion is a fully functional crypter alongside with a lot of useful features. The code of the stub can be modified by any means necessary to evade static and behavioral signatures. Please read the main page to learn about the two-layer architecture and how it helps minimizing the amount of code that needs to be changed in order to fix detection issues.
18+
19+
**The bottom line is:** With sufficient programming and reverse engineering skills, you will be able to derive your own "private stub". As long as you use non-distributing AV scanners and keep the stub to yourself, it will remain FUD much longer as compared to changes that I make publicly available to everyone.
20+
21+
If you do not have sufficient skills to do this, I would recommend looking for alternative products.

0 commit comments

Comments
 (0)