Hier ein Aurastacking script für den Patch 1.13
Aber vorab erstma:
Mit dem Patch 1.13 wurde nur der Torch anni trade stack gefixt nicht aber das merc stacking :D.
Der dank geht an die Blizzhackers
Das script is komplett Virusfrei! Es werden zwar einige Sachen als irgendwas angezeigt aber das kann bei Autoit passieren. Ich selber verwende es und habe 3 Virenschutzprogramme ( Norton , Kaspersky , Antivir )
So jetz aber zum Script
Hier erstma die Anleitung ( erstma auf Englisch werde bis zum Wochenende Deutsche uppen ) ist auch im upload nochmal drinne.
Und hier das script :
[Only registered and activated users can see links. Click Here To Register...]
Aber vorab erstma:
Mit dem Patch 1.13 wurde nur der Torch anni trade stack gefixt nicht aber das merc stacking :D.
Der dank geht an die Blizzhackers
Das script is komplett Virusfrei! Es werden zwar einige Sachen als irgendwas angezeigt aber das kann bei Autoit passieren. Ich selber verwende es und habe 3 Virenschutzprogramme ( Norton , Kaspersky , Antivir )
So jetz aber zum Script
Hier erstma die Anleitung ( erstma auf Englisch werde bis zum Wochenende Deutsche uppen ) ist auch im upload nochmal drinne.
Code:
How to use this script:
1. uncompress all files
2. run aes-decrypt.exe
3. the data is now decrypted and ready to use
4. when stackign make sure to have invintory screen up + merc screen
I have hardcoded the hotkeys
esc = scirpt close or exit
F8 = stacks helm
F9 = stacks armor
F10 = stacks shield
===================
new script addon:
==================
Home = pause function
this function will pause the script by starting a while 1 loop and this can be moderate to high computer memory intensive.
The reason why I did not add this function to the orginal script was for a time the basic script was open source. with a complete script
redo it now functions much much faster and does not use absolute x,y choords but now relitive to the window. If you are using this scirpt
on a closed computer terminal this script might not function properly because the window would never really be focused. Future revisions to
this script will not use mousemove () or send () but control send and control click so we can click an inactive window. win api hooks is a nother great idea to make this program work ultra fast but since warden is on and loading/scanning it might not be the best idea to rework the entire script around windows api.
If you come accross any software errors or find a bug feel free to send me a pm so I can hotfix this scirpt.
10/18/2010
-added pause function
-reduced script size
-added aes file encryption
-reduced autoit false positives from 9 flags to 5
-added aes file decrypt
-added keybind "home" set to pause
-removed file being in exe format
-added aes encrypted document
-removed outdated txt file on av mis flag
-adding 10/18/2010 virustotal scan:
0 VT Community user(s) with a total of 0 reputation credit(s) say(s) this sample is goodware. 0 VT Community user(s) with a total of 0 reputation credit(s) say(s) this sample is malware.
File name:
U-Stack-security hardened.zip
Submission date:
2010-10-18 08:31:36 (UTC)
Current status:
queued (#8) queued (#8) analysing finished
Result:
5/ 43 (11.6%)
VT Community
not reviewed
Safety score: -
Compact
Print results
Antivirus Version Last Update Result
AhnLab-V3 2010.10.18.01 2010.10.18 -
AntiVir 7.10.12.233 2010.10.18 -
Antiy-AVL 2.0.3.7 2010.10.18 -
Authentium 5.2.0.5 2010.10.17 -
Avast 4.8.1351.0 2010.10.17 -
Avast5 5.0.594.0 2010.10.17 -
AVG 9.0.0.851 2010.10.17 -
BitDefender 7.2 2010.10.18 -
CAT-QuickHeal 11.00 2010.10.18 -
ClamAV 0.96.2.0-git 2010.10.18 PUA.Script.Packed-3
Comodo 6427 2010.10.18 -
DrWeb 5.0.2.03300 2010.10.18 -
Emsisoft 5.0.0.50 2010.10.18 -
eSafe 7.0.17.0 2010.10.17 -
eTrust-Vet 36.1.7917 2010.10.18 -
F-Prot 4.6.2.117 2010.10.17 -
F-Secure 9.0.16160.0 2010.10.18 -
Fortinet 4.2.249.0 2010.10.18 -
GData 21 2010.10.18 -
Ikarus T3.1.1.90.0 2010.10.18 -
Jiangmin 13.0.900 2010.10.18 -
K7AntiVirus 9.66.2760 2010.10.15 -
Kaspersky 7.0.0.125 2010.10.18 -
McAfee 5.400.0.1158 2010.10.18 -
McAfee-GW-Edition 2010.1C 2010.10.18 -
Microsoft 1.6201 2010.10.18 -
NOD32 5540 2010.10.17 Win32/Packed.Autoit.E.Gen
Norman 6.06.07 2010.10.17 -
nProtect 2010-10-18.01 2010.10.18 -
Panda 10.0.2.7 2010.10.17 -
PCTools 7.0.3.5 2010.10.18 -
Prevx 3.0 2010.10.18 -
Rising 22.69.04.03 2010.10.15 -
Sophos 4.58.0 2010.10.18 -
Sunbelt 7084 2010.10.18 -
SUPERAntiSpyware 4.40.0.1006 2010.10.17 Trojan.Agent/Gen-Goo.Process
Symantec 20101.2.0.161 2010.10.18 -
TheHacker 6.7.0.1.060 2010.10.18 -
TrendMicro 9.120.0.1004 2010.10.18 -
TrendMicro-HouseCall 9.120.0.1004 2010.10.18 -
VBA32 3.12.14.1 2010.10.18 Trojan.Autoit.F
ViRobot 2010.10.18.4098 2010.10.18 -
VirusBuster 12.69.3.4 2010.10.17 Worm.Autoit.Gen
==============================================
the following are a faluse positive
==========================================
VirusBuster 12.69.3.4 2010.10.17 Worm.Autoit.Gen
VBA32 3.12.14.1 2010.10.18 Trojan.Autoit.F
SUPERAntiSpyware 4.40.0.1006 2010.10.17 Trojan.Agent/Gen-Goo.Process
NOD32 5540 2010.10.17 Win32/Packed.Autoit.E.Gen
ClamAV 0.96.2.0-git 2010.10.18 PUA.Script.Packed-3
==================================
autoit open source compression packer:
=========================================
http://www.autoitscript.com/forum/index.php?showtopic=34658
AutoIt has no virii installed on your system, and if a script you have created has been marked as a virus, (and you're not malicious) then this is a false positive. They found a set of instructions in an AutoIt EXE out there somewhere, took the general signature of the file, and now all AutoIt EXE's are marked (or most of them). This can be due to several reasons.
* AutoIt is packed with UPX. UPX is an open source software compression packer. It is used with many virii (to make them smaller).
* Malicious scripter got the AutoIt script engine recognized as a virus.
And I am sure there are more ways your executable could be marked, but that covers the basics.
Now I am sure you are wanting to know what you can do to get back up and running without being recognized as a virus. You have to send in a report to the offending AV company alerting them to the false positive they have made. It never hurts to send in your source code along with a compiled exe, to help them realize their mistake.
You may have to wait up to 24 hours for them to release an update. The time it takes really depends on the offending AV company.
[Only registered and activated users can see links. Click Here To Register...]