I seek to buy a loader for use in an opening strait. Projects can be already completed or ready in a short (1-3 weeks) timeframe. If the idea is very good, will wait longer. MUST is for necessary, MIGHT is for could be, depends on price, other variables. Please note: the team will need 3-10 days (depending on price) to assemble the payment, even for a ready-built project. I can provide contacts at neighbor forums and a deposit will be made as soon as is possible. We will work with the guarantor. The team has Russian and English speakers. We are prepared to spend up to 10,000k USD, but given that no advanced persistence is sought and we are comfortable with the use of WINAPI/STDLB, we are expecting to pay somewhere closer to 5k, with a higher price corresponding to added functionality.
You are: Confident in your work, take pleasure in collaboration, respect the intelligence of others, experienced in malware development. Please be able to work closely with highly experienced technicians throughout the project's life.
Language: Native/Assembly
Support: Ongoing, term negotiable
Functionality:
--Must load EXE from link.
--Might load locally
--Might load DLL, PS1, BAT
--Must allow for the distribution of traffic according to specific file, number of runs, and GEO.
--Must allow for simultaneous loading of multiple files
--Must have a kill after run option
--Might distribute for the distribution of traffic according to other categories (OS especially)
--Must have guest statistics.
--This strait will have the file dropped to disk and executed by the user outside of an 'exceptions' folder, so the dev should take caution to optimize execution and clean runtime performance with this in mind.
--Loads will be distributed as they arrive at the loader, so enhanced persistence is only necessary to extend the life of the software, not to hold bots for a longer period of time.
Stub:
--File should be small but need not be so small that it flags AV. We don't need a 17 kb stub, and are not expecting one.
--A size between 500 kb and 2-2.2 MB is fine.
--File should be optimized for quiet, clean execution and runtime in contemporary windows architectures, with best practices used to evade AMSI, smartscreen, and Defender. Developers with experience coding against the more common AVs are highly sought, and anyone with a ready solution for crypting as well will go to the front of our line. Your file needs to be cryptable, though, by you or by our crypter, who does not have a problem with the vast majority of native software.
--Dev should be prepared to collaborate if necessary with our crypter, who is pleasant to work with.
--EXE is necessary, DLL we don't care, PS1 is nice but not needed.
First contact is via forum PM. Please leave your preferred contact (telegram/xmpp) or request ours. Please do not contact past contacts from the user profile.
Thank you for your time.
You are: Confident in your work, take pleasure in collaboration, respect the intelligence of others, experienced in malware development. Please be able to work closely with highly experienced technicians throughout the project's life.
Language: Native/Assembly
Support: Ongoing, term negotiable
Functionality:
--Must load EXE from link.
--Might load locally
--Might load DLL, PS1, BAT
--Must allow for the distribution of traffic according to specific file, number of runs, and GEO.
--Must allow for simultaneous loading of multiple files
--Must have a kill after run option
--Might distribute for the distribution of traffic according to other categories (OS especially)
--Must have guest statistics.
--This strait will have the file dropped to disk and executed by the user outside of an 'exceptions' folder, so the dev should take caution to optimize execution and clean runtime performance with this in mind.
--Loads will be distributed as they arrive at the loader, so enhanced persistence is only necessary to extend the life of the software, not to hold bots for a longer period of time.
Stub:
--File should be small but need not be so small that it flags AV. We don't need a 17 kb stub, and are not expecting one.
--A size between 500 kb and 2-2.2 MB is fine.
--File should be optimized for quiet, clean execution and runtime in contemporary windows architectures, with best practices used to evade AMSI, smartscreen, and Defender. Developers with experience coding against the more common AVs are highly sought, and anyone with a ready solution for crypting as well will go to the front of our line. Your file needs to be cryptable, though, by you or by our crypter, who does not have a problem with the vast majority of native software.
--Dev should be prepared to collaborate if necessary with our crypter, who is pleasant to work with.
--EXE is necessary, DLL we don't care, PS1 is nice but not needed.
First contact is via forum PM. Please leave your preferred contact (telegram/xmpp) or request ours. Please do not contact past contacts from the user profile.
Thank you for your time.