How to "find" BTC


SUBMITTED BY: kenigma

DATE: Dec. 2, 2020, 3:51 p.m.

FORMAT: Text only

SIZE: 34.6 kB

HITS: 512

  1. HOWTO STEAL
  2. BITCOIN 4.0
  3. Table of Contents
  4. 1Foreword...........................................................................................................3
  5. 2Justification........................................................................................................4
  6. 3Introduction.......................................................................................................5
  7. This guide is NOT for you if..............................................................................5
  8. This guide is for you if.....................................................................................5
  9. 4The development process of the guide.............................................................6
  10. 5Awesome tutorial video.....................................................................................6
  11. 6Keep in mind before you start...........................................................................7
  12. 7Get a safe bitcoin wallet and learn how to launder your coins..........................8
  13. Store your coins...............................................................................................8
  14. Steps:...........................................................................................................8
  15. Laundering......................................................................................................8
  16. The most common way to launder coins is Blockchain.info Shared Coins...8
  17. The most secure way to launder your coins is through anonimous altcoins9
  18. 8Generate a bunch of addresses......................................................................10
  19. Notes:........................................................................................................11
  20. Testing the Mass Address Generator.............................................................11
  21. 7.Create your own BITCOIN STEALER malware.................................................13
  22. 9Testing your malware......................................................................................21
  23. 10Remove the malware....................................................................................22
  24. 11Summing up: how the malware works..........................................................23
  25. 12Experiences / FAQs / ideas............................................................................24
  26. 1 Foreword
  27. My motivation is purely technical. I am using this method over a year with
  28. huge success. About half a year ago I wrote the first version of this guide and
  29. started to sell it in Evolution. The reason was because I got stucked and lazy
  30. and was not developing the method further, but when I put it on the market, I
  31. suddenly recieved a bunch of feedback. My guide quickly became one of the
  32. most popular item on Evo, as a result I gained back my motivation and
  33. amazing things were happening with not just this software but with my wallet,
  34. too. But after that Evolution exit scam happened and I decided to buy some
  35. flight ticket and go on a crazy holiday until a nice new market emerges. The
  36. time has come and I am back.
  37. So do not get fooled and think, because of the cheap price, this
  38. guide does not worth shit, in fact, I am not aware of any guide
  39. in the market that would be more valuable than this one. As I
  40. said, my motivation is to develop further this method and I don't
  41. give a fuck about thaose few bitcoins I can get out of this
  42. market.
  43. 2 Justification
  44. When a system get attacked it becomes more resilient.
  45. I honestly hope this method will not work in 2-3 years from now, but if we
  46. don't attack it now, then someone will do it, after my grandpa and your
  47. grandma start to use bitcoin and that would be a huge disaster.
  48. You have to attack bitcoin in order to make it better.
  49. 3 Introduction
  50. It is an easy-to-follow, comprehensive, step-by-step guide. If you follow this
  51. you will never have to worry about finances again.
  52. This is an advanced, tested, professional hacking method. This is the first (and
  53. right now the only) guide that makes it possible the first time for an average
  54. person to use this classic and effective method.
  55. This software is unique, developed by me. The reason why this method is not
  56. being used by the average Joe is because you actually have to hardcode your
  57. btc address into the program and then build the project by yourself.
  58. The good news are, if you have the source code and clear instructions, it is not
  59. difficult at all.
  60. The package contains the source code (C#) of a malware (BITCOIN STEALER)
  61. that watches Windows clipboard for Bitcoin addresses and replaces
  62. them with your own. So the target will send the coins to you by
  63. mistake.
  64. Also there is a trick that makes your bitcoin address looks similar to
  65. the copied address...
  66. For example, if the target's address is like this:
  67. 1JRCnFwbr4wwtzGJ1gkqpVgwCZg9MSwdJE
  68. Yours will be like this:
  69. 1JRCfyjr1yvZzH9JuoEYZyYY5tWconhyhpgIE
  70. An other advantage of having the source code is that it keeps you safe (from
  71. me), because you can revise it by yourself, also you can trust it has been
  72. revised by others many times before.
  73. This guide also will show you how to use this software effectively. The package
  74. will show you the social engineering and phishing methods in order to reach
  75. your goal.
  76. Your only goal is to make the targets to run your exe and from there you can
  77. lay back in the rest of your life, go to Malibu and watch the money flowing in.
  78. This guide is NOT for you if
  79. • you want to invest your money into illegal activity
  80. • you want to take risk
  81. This guide is for you if
  82. • you are average person, who wants to make easy money
  83. • you are an average techie, who wants to know how to use an advanced
  84. hacking technique
  85. • you are a programmer, who needs the source code of a masterpiece
  86. 4 The development process of the
  87. guide
  88. It is important to know, the developement of this software is continious. As it
  89. becomes more and more powerful tool, the price will raise simultaneously.
  90. Well, I have good news for you. If you buy this product and then contribute to
  91. its forum topic you'll get the next version for free, you don't even have to buy
  92. the price difference. All you have to do is to send me a pm with a link to your
  93. forum post when you notice a new version is out.
  94. 5 Awesome tutorial video
  95. Wakawakala9 made a nice tutorial video. It won't be compatible with newer
  96. versions, but it will definitely help you get some idea.
  97. https://www.youtube.com/watch?v=kTVJna6VhuA
  98. 6 Keep in mind before you start
  99. I know there are so many bullshit and poorly written article on the internet
  100. and people tend to rush through them. This is not one of them. You have to
  101. read and follow it carefully and you will make money. Do not rush, it won't be a
  102. waste of time!
  103. 7 Get a safe bitcoin wallet and learn
  104. how to launder your coins
  105. Assuming you have bought this guide on the black market, there is a big
  106. chance you already have a reliable wallet, that nobody knows is yours, but let
  107. me say the truth, most of you guys are so careless.
  108. The coin laundering extremely critical here here, because you are about to
  109. steal other people's money and I bet they will try to follow you on the
  110. blockchain.
  111. Store your coins
  112. I recommend using blockchain.info wallet over TOR, because it has onion
  113. address. (http://blog.blockchain.com/2014/12/03/improved-security-for-torusers/)
  114. You can also store your coins on a desktop wallet, too, it is your decision, but
  115. right now I cannot recommend any other web wallet that would have an onion
  116. address. This is critical, because it will keep your money safe from malicious
  117. TOR exit nodes.
  118. Steps:
  119. 1. Use TOR browser
  120. 2. Go to the onion address of the blockchain.info wallet:
  121. https://blockchainbdgpzk.onion/
  122. 3. Create a wallet for the coins you steal.
  123. Laundering
  124. However the common belief is that bitcoin mixing techniques are just fine and
  125. they works and maybe they are right about that, my belief is different.
  126. The most common way to launder coins is
  127. Blockchain.info Shared Coins
  128. example:
  129. btc address -> blockhain.info shared send -> an other btc address
  130. *note: DarkWallet will be nice and might be the ultimate solution, but it's too
  131. baby to use it yet. If not neccessary, don't use anything that's not stable.
  132. The most secure way to launder your coins is
  133. through anonimous altcoins
  134. There are some stealthy anonymous coins like Darkcoin (DRK) and Monero
  135. (XMR). They are working. I cannot tell too much about other anoncoins, since I
  136. did not looked into them.
  137. NOTE: DRK has been renamed to DASH, because its developers are a
  138. bunch of pussy. Fuck them I'm not going to use that name.
  139. So there is this amazing service, called Shapeshift from Erik Voorhees.
  140. No account needed, only an altcoin address and an amount and you can send
  141. there bitcoin.
  142. example:
  143. btc address -> blockhain.info shared send -> shapeshift.io -> drk
  144. address -> DarkSend-> shapeshift.io -> btc address
  145. 8 Generate a bunch of addresses
  146. «Are you insane? Why would I do that?» you ask... Listen, here is the trick. You
  147. want your bitcoin address to look similar to the target's copied adress. Then
  148. let's create a bunch of addresses first and let our malware to choose the most
  149. similar one.
  150. You'll need my Mass Address Generator, that I've written for this. You can find
  151. it in the package, accompanied by it's source code.
  152. /*
  153. Programmer's note: If you want to build the source yourself,
  154. you can do it in exactly the same way that you'll do it with
  155. the Bitcoin Stealer application in the following sections of
  156. this guide.
  157. The only differences are, the project has to be in at least
  158. .NET4.5 and you'll need two NuGet package: NBitcoin and the
  159. Blockchain.info's API
  160. */
  161. To run this app, you'll need to install the .NET 4.5 framework.
  162. https://www.microsoft.com/en-us/download/details.aspx?id=30653
  163. Set how many addresses you want to generate and press start, you're
  164. cool. You've just generated a bunch of bitcoin addresses and their secret
  165. key pairs. I'd recommend you at first start with 100 addresses for testing
  166. purposes.
  167. After you've generated your addresses, at the « Wallet » tab, with the
  168. « Refresh » button you can check if there are some not empty among them.
  169. (There won't be, until sb send money to it.)
  170. • If you've generated 100 000 addresses, refreshing will take for a day.
  171. • If you've generated 10 000 addresses, refreshing will take for about
  172. 40min.
  173. • Refreshing 100 addresses takes less than a minute.
  174. Generated files :
  175. addressSecretPairs.txt – stores all the generated addresses and
  176. their corresponding secret keys.
  177. vanityAddresses.txt – stores all the generated addresses only.
  178. This is what our malware will need.
  179. notEmptyAddresses – stores not empty addresses and their
  180. corresponding secret keys. When you click « Refresh » it will
  181. generate this file.
  182. Notes:
  183. • When you generate new files, they'll overwrite the old ones.
  184. • You probably wants to store them safely and make a backup.
  185. Testing the Mass Address Generator
  186. 1. Open the program, click start. This will generate 100 addresses and their
  187. corresponding secrets.
  188. 2. Check out generated addresses. Send a small amount, like (0.0001btc) to
  189. one of them.
  190. 3. When the coins has arrived, change to the « Wallet » tab and click
  191. « Refresh ».
  192. 4. Check out not empty addresses ! (Format: address:secretKey)
  193. 5. Go to your Bitcoin wallet and import the secret key. (Preferably
  194. Blockchain.info (https://blockchainbdgpzk.onion/)
  195. It's extremely easy, 3 click :
  196. You click « I Understand », because you're an advance user. (If they'd
  197. have any idea how advanced you are:)
  198. 6. Congratulations ! You're done, you can spend the money.
  199. 7. Create your own BITCOIN STEALER
  200. malware
  201. This is the core of the guide. It's time to do the geeky stuff. We're gonna
  202. change a few lines in the code and build our C# project. After this you can write
  203. it into your CV. Wait... what?
  204. First of all, you have to know C# is a Microsoft slave language. This means,
  205. from now on we're working on Windows. More accurately, we're going to code
  206. in .NET Framework 4.0, that means you have to use Windows XP SP3 or higher
  207. version (like Windows 7,8).
  208. If you don't have Windows I recommend you to use VirtualBox
  209. (https://www.virtualbox.org/). You install it, then you set up a Windows virtual
  210. machine in it.
  211. Note: it is important to use the latest version of VirtualBox
  212. Next we need to get the Visual Studio.
  213. I recommend you to use the Visual Studio Community version.
  214. http://www.visualstudio.com/
  215. Note: the Visual Studio is the longest taking installing software
  216. in the whole world: (Ok, it's not, but you get the point.)
  217. Now, that we have set up the requirements it's finally time to code.
  218. From here you should follow these instructions very strictly, because if you are
  219. not familiar with coding, you can't make any mistake here. If you have done a
  220. mistake, delete everything and start this chapter from here again.
  221. 1. Run Visual Studio
  222. 2. File/New/Project/
  223. Select Templates/Visual C#/Windows Forms Application
  224. Select .NET Framework 4
  225. Name: Adobe Reader - you want to choose a name that is not suspicios
  226. for the a user when it is looking at the processes. I mean "BITCOIN STEALER"
  227. would be a very bad idea. However in this tutorial I will not show you how to go
  228. with an other name (eg. « chrome » or sth), if you don't want any conflict, just
  229. let it be "Adobe Reader". As you can see on the pictures, I was using
  230. « explorer », but it turns out to be not a good idea, because with this name it
  231. won't work on winxp.
  232. Programmers note: If you want to go with an other name find and
  233. change the «adobe» string everywhere in the solution. (ctrl+F,
  234. search in whole solution)
  235. Solution name: Adobe Reader
  236. Location: here you want to select some folder that you'll never let
  237. anybody to see.
  238. 3. In the Solution Explorer rename the "Form1.cs" to "BackgroundForm.cs".
  239. 4. Open the project folder (Adobe Reader).
  240. 5. Open the Bitcoin Stealer/sources (it's next to this pdf what you're reading
  241. right now).
  242. 6. Copy and replace everything from Bitcoin Stealer/sources folder to the
  243. project folder (Adobe Reader).
  244. 7. Right click on Adobe Reader / Add existing Item...
  245. 8. Select Program.cs and Tools.cs from the project folder (Adobe Reader).
  246. 9. Right click on project (Adobe Reader) / select Properties.
  247. Note: On some picture the name of the project is «AdobeUpdate»
  248. instead of «explorer». Do not get confused by that.
  249. 10. Select Resources / click Add Resource from Existing file.
  250. 11. Choose your vanityAddresses.txt you've just generated with the
  251. MassAddressGenerator.
  252. 12. Set Access Modifier to «Public»
  253. 13. There is one more last setting we want to set. We want to build our project
  254. in Release mode.
  255. Programmer's note: you can use choose Debug mode if you want
  256. to mess around with the code.
  257. If you use debug, then you don't need to remove the malware
  258. from your computer, since it doesn't copy itself into it and
  259. will not start with the Windows.
  260. 14. Now it's time to build our solution. If we have done everything right we
  261. won't get any error here.
  262. Congratulations, you've created your first malware, now you're officially a
  263. hacker. You can tell everybody about it. Wait... what?
  264. 9 Testing your malware
  265. Now it's time to do the testing.
  266. First locate the exe file: Adobe Reader/bin/Release/Adobe Reader.exe (you can
  267. rename it as you wish). From here you won't need any other file to work with,
  268. only the executable.
  269. 1. Copy the exe to your Desktop
  270. 2. Run the executable! (Attention: you're not going to see any welcome
  271. windows or anything, like that. Just imagine, how would you react if a
  272. window would pop up every time you start your computer with a
  273. message like this: "Hey man, what's up?! I'm a virus, I've infected your
  274. computer... sucker.")
  275. 3. Check if our program is running: Windows Task Manager/Processes.
  276. (Press ctrl+shift+esc) Here you should see "Chrome32.exe" program is
  277. running.
  278. 4. Now copy a bitcoin address and paste it somewhere. Does it work? No?
  279. Do it again WITH AN OTHER ADDRESS! Still don't work? Do it again with
  280. an other address! Repeat!
  281. The reason why it doesn't work all the time, because it would be too
  282. suspicios. Furthermore if you copy the same address twice, it won't work,
  283. too in order to avoid suspicion.
  284. There is a variable at the beginning of BackgroundForm.cs, called
  285. OppToMissDef. If you change it's value to 0, it will work every
  286. time (exept when you try to paste the same address twice)
  287. 5. Finally restart your computer and check if it starts running with the
  288. Windows. But now the name of the program will be "AcroRd32.exe" and
  289. not "Chrome32.exe". Why is that?
  290. When you run your exe it will copy itself somewhere on your
  291. computer and change it's name to Chrome32.exe and copy itself to
  292. somewhere else with a name as AcroRd32.exe. Then execute this
  293. Chrome32.exe, then delete itself.
  294. So now Chrome32.exe is running, but if the user is so smart, it
  295. will realize, "OMG, I've just launched a malware", so it goes to
  296. processes, find this Chrome32.exe, delete it and stop it.
  297. Well not quite yet. When the user next starts the windows, the
  298. AcroRd32 will run, even if it deleted the Chrome32.
  299. If you didn't understand what I was just saying, don't worry,
  300. it's my fault. It's enough to know, when the target launches the
  301. exe, it will delete itself.
  302. 10 Remove the malware
  303. Finally remove it from your computer:
  304. 1. Start Windows Task Manager and terminate the Chrome32.exe or
  305. AcroRd32.exe process!
  306. 2. Go to %appdata% in your file browser.
  307. 3. Delete AppData/Roaming/Adobe (x86) folder.
  308. 4. Delete AppData/Local/Google (x86) folder.
  309. If you don't terminate the malware manually, as it is described
  310. in the first point you can't delete one of the folder.
  311. If you've deleted the Adobe folder it won't start again on your
  312. computer, so you're good, but to completly remove it you have to
  313. do one more thing:
  314. • Start the Registry Editor (regedit) and delete our software from
  315. "HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Ru
  316. n"
  317. If you don't find it, check HKEY_LOCAL_MACHINE instead of
  318. HKEY_CURRENT_USER
  319. 11 Summing up: how the malware
  320. works
  321. You only have a standalone exe file. You can rename it to anything. Let's say
  322. InnocentSoftware.exe.
  323. Someone click on InnocentSoftware.exe, then it will disappear. What happens
  324. is, InnocentSoftare.exe copies our malware to AppData/Roaming/Adobe
  325. (x86)/AcroRd32.exe and AppData/Local/Google (x86)/Chrome32.exe and make
  326. sure AcroRd32.exe starts with Windows every time.
  327. Then it starts Chrome32.exe.
  328. Then InnocentSoftware.exe stop running.
  329. Then Chrome32.exe deletes InnocentSoftware.exe.
  330. When the user copies a btc address then it pastes yours instead of the user's.
  331. Furthermore, it will look similar to the the copied address.
  332. However there are some mechanisms in place in order to avoid suspicion, for
  333. example when the user copies the same address twice in a row the copypaste
  334. will work normally and it will only work for every 3rd opportunities. (Or
  335. whatever what you set the OppToMissDef in the BackgoundForm.cs file)
  336. For better understanding you might also want to take a look at
  337. the BackgroundForm.cs file's comments (and maybe the code).
  338. 12 Experiences / FAQs / ideas
  339. blowmoney1996
  340. This guide is great. Stole about 2.3 btc already. This is the
  341. fuckin shit. He delivered it within 5 min and is a great vendor.
  342. real_barreface
  343. Got the guide within an hour of ordering and scammed 5 BTC in 2
  344. days. Learn to spread this and your good
  345. Scheynkine
  346. fun fact #1
  347. got robbed today from my own malware.
  348. ...
  349. not robbed exactly, i just wanted to transfer from wallet to evo.
  350. instead it ended up in the scam-wallet.. i thought i deleted it,
  351. but i didnt clear the appdata. but it's great, that it really
  352. works!
  353. What about Anti virus softwares, do they detect it?
  354. It is a pretty "harmless" software, you won't have any problem
  355. with it. It does not communicate with the internet, or does
  356. anything fairly suspicious.
  357. gavioesdafiel
  358. Hi All,
  359. I just have started my learning process to spread/spam this
  360. malware. As i dont have too many skills on that Im getting some
  361. basics tips that I wanted to share with you. I appreciate any
  362. kind of information/tips that you can share with me. |o|
  363. "
  364. 11 Hacks to Increase Your Email Open Rates
  365. The grim reality of email marketing is that very few people
  366. actually pay attention to the messages they receive. Email is
  367. the primary mode of communication for so many businesses that an
  368. opt-in just doesn’t have the value it once did. 100 people might
  369. claim they want your newsletter, but when it comes time for the
  370. mental investment of opening it and reading what’s inside, maybe
  371. 5-10 of them actually do.
  372. 1. Make sure your newsletter looks good.
  373. The idea behind this hack is that, when a user signs up for your
  374. mailing list, they’re going to open the first message you send.
  375. If they open that message and they discover a newsletter that
  376. looks broken or skewed, they’ll figure your message is broken in
  377. some way. Maybe they’ll let you know, maybe they’ll just delete
  378. the message. Either way, that bad experience lingers, and the
  379. next time a newsletter comes by it languishes in their inbox.
  380. You can test your newsletters using Litmus, to see how it will
  381. look on various platforms, including mobile. Litmus will also
  382. tell you if something in your message or subject line will trip
  383. spam filters.
  384. 2. Keep your subject lines short.
  385. According to a survey presented by Salesforce, your email open
  386. rates will almost definitely be much higher when your subject
  387. line is short. A subject line under 10 characters is enticing
  388. enough to give you a nearly 60% open rate on average. Chances
  389. are this is well above what you typically experience.
  390. What can you do in ten characters? You only have two or three
  391. short words to play with. Fortunately, short language is
  392. enticing on its own. In a world of subject lines that run long
  393. enough to be truncated, a short subject line stands out. It
  394. almost doesn’t matter what you write.
  395. 3. Use title case capitalization in your subject line.
  396. Use-title-case-capitalization-in-your-subject-line
  397. It’s much more attention-grabbing to use title case – that is,
  398. Capitalization of the First Letter of Each Major Word – in your
  399. subject line than it is to use a standard sentence. Treat your
  400. email subject line in the same way you might treat the title of a
  401. blog post for your rich snippet. While a subject line should be
  402. short, it doesn’t have to be, and a compelling question can break
  403. the length rule and maintain a high open rate.
  404. 4. Send and send and send again.
  405. Whenever you send out a message, track who opens it and who
  406. doesn’t. Anyone who doesn’t open it should be added to a new
  407. list of people you can target again. If they don’t open your
  408. message, it’s as though they never saw it in the first place. It
  409. might be buried in their inbox, they might have deleted it
  410. without thinking or it might have ended up in an archive. In any
  411. case, you can safely send the email a second time, potentially
  412. drawing quite a bit of additional attention. You may not want to
  413. send a third time, however; the rule of threes lends extra
  414. potency to a third dismissal.
  415. You might like:
  416. How to Turn Your Mailchimp Subscribers Into CustomersHow to Turn
  417. Your Mailchimp Subscribers Into Customers Your mailing list, as
  418. powered by Mailchimp, is one of…
  419. 5. Proof your message, and have someone else do it.
  420. When you spend a lengthy amount of time working on a single
  421. project, you grow a sort of mental blindness to its flaws. Your
  422. mind fills with the concepts and thoughts behind each word you
  423. write, rather than what you write itself. In the end, you might
  424. end up with a message you think is perfect, with a prominent typo
  425. you keep missing. Enlist the aid of someone, it doesn’t matter
  426. who; just someone who will put a second pair of eyes on the piece
  427. and proofread it for you.
  428. 6. Satisfy the subject line.
  429. The point of a subject line, at least a good one, is to stir
  430. thoughts in the reader. Your goal is to make them ask what could
  431. possibly come as a follow-up from that subject line, with the
  432. promise that the answer is inside the email.
  433. That means you need to live up to your promise and follow up on
  434. your subject line in the message itself. You can’t draw in
  435. attention with one concept, only to disregard it in the body;
  436. it’s a bait and switch that leaves users disappointed.
  437. 7. Invite replies.
  438. Invite-replies
  439. Here’s one thing you don’t see every day; “If you have any
  440. questions, feel free to respond to this message.” Most emails
  441. from large companies are sent from automated accounts that no one
  442. checks. Users are used to needing to find your contact
  443. information on your site if they have a question, and that’s too
  444. much work. It means a lot of questions go unanswered. Instead,
  445. open up your newletter as a two-way communication. Even if you
  446. then forward the replies you get to your customer service email
  447. address, you’re still giving users a direct route back to you.
  448. 8. Use bright, colorful buttons for your CTA.
  449. Your call to action should be preceded by a question, and it
  450. should take the form of a bright colored button. Users tend to
  451. gloss over plain text links in their emails, just as they do on
  452. your landing page. And, just like your landing page, you need to
  453. optimize your CTA in the newsletter. After all, it’s the
  454. newsletter that helps funnel traffic to your landing page.
  455. 9. Segment your newsletter mailing list and test variations.
  456. Split testing isn’t just for ads or landing pages; you can split
  457. test your newsletters as well. Segment your audience into groups
  458. and send variations on your message to each. Try to keep
  459. representative groups if you’re testing general changes, like
  460. tweaks to your subject line or the color of your CTA button. You
  461. might skew your results if you segment by demographics to run
  462. your tests.
  463. 10. Don’t forget the other messages you send.
  464. When a user decides to download your white paper or ebook, do you
  465. send them a confirmation email and thank-you letter? If so, you
  466. might be missing out on a great opportunity. Consider that
  467. content delivery message as a chance to include more hooks for
  468. future actions, both in the immediate short term and the long
  469. term. There’s always something you can encourage the user to do
  470. to support your brand.
  471. 11. Maintain a consistent voice.
  472. Users feel like they’re interacting with an impersonal, robotic
  473. corporate face if they receive drastically different messages
  474. from different marketing channels. If their experience with
  475. customer service is much more casual, how are they to trust that
  476. it’s not some outsourced company doing the work? A consistent
  477. voice allows them to trust your business that much more.
  478. He man, i messed around with your V1 of the bitcoin stealer and
  479. got deeper in the spreading method.
  480. I found some method to spread it that works for me so i want to
  481. share it to you.
  482. I hide the .exe in a .rar with images and changed the .exe to
  483. .jpg and changed the icon from .exe to the one of .jpg , so you
  484. don't see the .exe file until you click the image but then its
  485. already to late wink
  486. I have a little not proud method to spread this .rar file with
  487. images , i do it on teen chat sites and login as female and ask
  488. if they want to see pictures.
  489. So far your method give me like $200,- , i want to thank you for
  490. that !
  491. I've gave some thought to this. Maybe you can scam some pedos
  492. with it. Upload the pics and write a post to a pedo forum. Pedos
  493. probably use bitcoin, cos they're on tor.
  494. 1.0 review
  495. TheSaint
  496. So, I finally found time for this.
  497. Nothing much to say. The guide might be confusing to a complete
  498. newb, I wouldn't call it total noob friendly, however it is easy
  499. to follow and the whole thing can be done in about 3 minutes,
  500. from the moment You get all the tools on point.
  501. This stealer MIGHT steal something, but it needs spreading. And
  502. spreading is pain. If You are willing to bare the pain, I rather
  503. recommend setting up a rat or a botnet as it's way more
  504. profitable and fun. But then You need to crypt it (preferably
  505. FUD) and that would cost something.
  506. To sum things up - This is bitcoin stealing for noobs.
  507. The Guide - 4/5 (could be more noob friendly)
  508. The program - 3/5 (I saw that You are twisting it, so it might
  509. get better)
  510. PS. I check the addresses like 5 times, so I would never fall for
  511. this.
  512. Think about that.
  513. Cheers.
  514. 2.0 review
  515. TheSaint
  516. I finally decided to look at the updated version. You've done a
  517. wonderful job here. With the 100000 addresses it will be even
  518. better. The guide is alright, it looks a bit messy though, but
  519. that's not a problem. The stealer is amazing, works flawlessly.
  520. Now, I don't know if this is possible, but I'd love to see this
  521. stealer infecting usb sticks. That would spread it like a plague.
  522. What this really needs is a FUD Crypter, binder and extension
  523. spoofer.
  524. The very best thing about this tool, is that it can't be traced
  525. back to You, rather than a botnet for instance.
  526. I thank You for your work.
  527. Waiting for more updates.
  528. Cheers!
  529. Virtualbox vs Visual Studio
  530. swimmar
  531. Currently attempting to see it work in real-time, but I am using
  532. a virtual machine and it seems to not like that.. will keep
  533. trying and use a real machine as well.
  534. funWithCodes
  535. There are some memory corruption problems I know about with
  536. virtualbox and visual studio together, the solution is to update
  537. the virtualbox for the newest version. I'm not sure there should
  538. be a problem with specifically with these softwares.
  539. swimmar
  540. Got it working. Updated virtualbox (as recommended... foolish
  541. mistake), but also set the auto-start in the configuration
  542. settings in Visual Studio.
  543. besmart
  544. if anyone can get a cracked version of this
  545. http://www.exejoiner.com/ would be great. Seems to be the perfect
  546. tool to make this stealer ready for spreading.
  547. Kefkalink777
  548. So, after about 1 week of using torrent services to spread files
  549. infected with this program, I have finally seen some success.
  550. Only got a little over $25 in bitcoin, which may not seem like
  551. much, but is much more than I have invested in this, and also
  552. PROVES that this malware works. For those who are interested, I
  553. used a free crypter/binder program called aegis crypter to bind
  554. the malware to other files, mostly cracked video game files, and
  555. also a few bitcoin mining programs. I then used Utorrent to turn
  556. those into torrent files, and uploaded the torrents to every
  557. sharing website I could find. The downside is, I am now banned
  558. from pretty much every single major torrent sharing site out
  559. there. If anyone has any experience with crypters, I am looking
  560. for an up-to-date FUD stub for the Aegis Crypter program.
  561. tl;dr This program works, confirmed. It's just really hard to
  562. effectively spread.
  563. Once i find a spammer to send out the malware. What will i give
  564. the spammer to send. Im guessing i piece together the malware via
  565. the coding instructions given, then submit the finished product
  566. to the spammer to send out?
  567. Exactly, as you've said. Only the exe what the spammer need.
  568. Do you have Jabber or ICQ?
  569. Sorry, I consider to be too risky the use of instant messaging
  570. apps.
  571. I saw on the forum that you give the update free to the buyers
  572. who bought it before?
  573. Yes, I do.
  574. btw, do not recommend bitfogger. they are a mess. read this:
  575. https://bitcointalk.org/index.php?topic=50037.340
  576. Does it work on Mac?
  577. No.
  578. Advices on how to get your malware running on other computers
  579. Now that we have everything what we need, it is time for action.
  580. The only goal of this chapter is to make people to run your exe.
  581. It is the interesting part, because you have to be creative from
  582. here, think about what you have, what you can use. In this
  583. chapter I'm going to give you ideas that you might haven't
  584. thought of.
  585. You can target specific people.
  586. A good tactic could be is to get a pendrive and put on the virus
  587. to every computer you meet. You'd be surprised how many there
  588. are. If somebody don't use Bitcoin don't hesitate he will
  589. eventually! That's even better, you know... mistakes of the
  590. beginners.
  591. Go to libraries, schools, net cafes, basically any place that has
  592. computers in it in your city.
  593. What about your company?
  594. Ask for help on deepweb forums. Team up with other people. Buy a
  595. hacking service or something...
  596. Read the guides I've included to the pack and get some ideas from
  597. there.
  598. Gotta tell you something funny that happen to me, I stole from
  599. myself, well, not exactly lol..This is how it happened, I
  600. executed the malware on my laptop just for a test, but forgot to
  601. totally delete it. So i'm doing this deal out of evo with
  602. somebody who wanted a ID scan, so he was like give me your wallet
  603. addy, I copied, and pasted it into ICQ messenger, and I didn't
  604. even think twice to check the address, just sorta just sent it. I
  605. wouldn't have noticed I gave him 1 of my vanity addresses until
  606. he said "You know you have fbi in your address?" ya know just for
  607. a little laugh, so I laughed an was like really? jokingly, so
  608. something told me to glance at the addy I copied, and seen it
  609. wasn't my copied address, but it was too late, he had already
  610. sent payment to it lol..
  611. Moral is, if I can just send that addy without even checking it,
  612. this malware is golden if spreaded right, bcuz if I was a victim,
  613. it would already be too late, an my coins would be gone.
  614. Now it's just the spreading I'm having issues with without it
  615. being detected. The binding is alright if your mark isn't too
  616. smart about downloads, and file types. My method was binding the
  617. malware with a actual real PDF carding guide,with a adobe icon.
  618. when you execute the file, the guide comes up, and the exe
  619. executes in the background, which is perfect BUT what gives it
  620. away is the file type being "Application" whenever they unpack
  621. the rar file, and then they are like, hey nice try asshole lol..I
  622. been doing some studying on how to crypt it, but haven't been
  623. lucky, bcuz I'm not good at coding in that department. what I've
  624. read so far, that's what's gotta be done for this to be
  625. effective. Hope you can come up with a solution. On the forum,
  626. that seems to be mostly everybodies only problem.
  627. noname
  628. Hey there,
  629. i wanted to check my adresses, if somebody transfered something
  630. to my faked adresses. but i accidentally pressed the wrong button
  631. and it generated new adresses. is there any way i can check the
  632. old ones?
  633. Regards
  634. funWithCodes
  635. I'm sorry, you've just lost your secret keys.

comments powered by Disqus