About EasySploit: EasySploit is Metasploit automation tool to use Metasploit Framework EASIER and FASTER than EVER. EasySploit's options:
Windows --> test.exe (payload and listener)
Android --> test.apk (payload and listener)
Linux --> test.py (payload and listener)
MacOS --> test.jar (payload and listener)
Web --> test.php (payload and listener)
Scan if a target is vulnerable to ms17_010 (EnternalBlue)
Exploit Windows 7/2008 x64 ONLY by IP (ms17_010_eternalblue)
Exploit Windows Vista/XP/2000/2003 ONLY by IP (ms17_010_psexec)
Exploit Windows with a link (HTA Server)
Contact with me - My accounts
EasySploit's installation You must install Metasploit Framework first. For Arch Linux-based distros, enter this command: sudo pacman -S metasploit For other Linux distros, enter these command to install Metasploit Framework: And then, enter these commands to install EasySploit:
How to use EasySploit? (EasySploit video series tutorials)
Disclaimer about EasySploit:
Usage of EASYSPLOIT for attacking targets without prior mutual consent is ILLEGAL. Developers are not responsible for any damage caused by this script. EASYSPLOIT is intented ONLY FOR EDUCATIONAL PURPOSES!!! STAY LEGAL!!! You might like these similar tools:
As of late I have been un-naturally obsessed with blockchains and crypto currency. With that obsession comes the normal curiosity of "How do I hack this and steal all the monies?"
However, as usual I could not find any actual walk thorough or solid examples of actually exploiting real code live. Just theory and half way explained examples.
That question with labs is exactly what we are going to cover in this series, starting with the topic title above of Re-Entrancy attacks which allow an attacker to siphon out all of the money held within a smart contract, far beyond that of their own contribution to the contract.
This will be a lab based series and I will show you how to use demo the code within various test environments and local environments in order to perform and re-create each attacks for yourself.
Note: As usual this is live ongoing research and info will be released as it is coded and exploited.
If you are bored of reading already and just want to watch videos for this info or are only here for the demos and labs check out the first set of videos in the series at the link below and skip to the relevant parts for you, otherwise lets get into it:
Background Info:
This is a bit of a harder topic to write about considering most of my audience are hackers not Ethereum developers or blockchain architects. So you may not know what a smart contract is nor how it is situated within the blockchain development model. So I am going to cover a little bit of context to help with understanding.I will cover the bare minimum needed as an attacker.
A Standard Application Model:
In client server we generally have the following:
Front End - what the user sees (HTML Etc)
Server Side - code that handles business logic
Back End - Your database for example MySQL
A Decentralized Application Model:
Now with a Decentralized applications (DAPP) on the blockchain you have similar front end server side technology however
Smart contracts are your access into the blockchain.
Your smart contract is kind of like an API
Essentially DAPPs are Ethereum enabled applications using smart contracts as an API to the blockchain data ledger
DAPPs can be banking applications, wallets, video games etc.
A blockchain is a trust-less peer to peer decentralized database or ledger
The back-end is distributed across thousands of nodes in its entirety on each node. Meaning every single node has a Full "database" of information called a ledger.The second difference is that this ledger is immutable, meaning once data goes in, data cannot be changed. This will come into play later in this discussion about smart contracts.
Consensus:
The blockchain of these decentralized ledgers is synchronized by a consensus mechanism you may be familiar with called "mining" or more accurately, proof of work or optionally Proof of stake.
Proof of stake is simply staking large sums of coins which are at risk of loss if one were to perform a malicious action while helping to perform consensus of data.
Much like proof of stake, proof of work(mining) validates hashing calculations to come to a consensus but instead of loss of coins there is a loss of energy, which costs money, without reward if malicious actions were to take place.
Each block contains transactions from the transaction pool combined with a nonce that meets the difficulty requirements.Once a block is found and accepted it places them on the blockchain in which more then half of the network must reach a consensus on.
The point is that no central authority controls the nodes or can shut them down. Instead there is consensus from all nodes using either proof of work or proof of stake. They are spread across the whole world leaving a single centralized jurisdiction as an impossibility.
Things to Note:
First Note: Immutability
So, the thing to note is that our smart contracts are located on the blockchain
And the blockchain is immutable
This means an Agile development model is not going to work once a contract is deployed.
This means that updates to contracts is next to impossible
All you can really do is createa kill-switch or fail safe functions to disable and execute some actions if something goes wrong before going permanently dormant.
If you don't include a kill switch the contract is open and available and you can't remove it
Second Note:Code Is Open Source
Smart Contracts are generally open source
Which means people like ourselves are manually bug hunting smart contracts and running static analysis tools against smart contract code looking for bugs.
When issues are found the only course of action is:
Kill the current contract which stays on the blockchain
Then deploy a whole new version.
If there is no killSwitch the contract will be available forever.
Now I know what you're thinking, these things are ripe for exploitation.
And you would be correct based on the 3rd note
Third Note: Security in the development process is lacking
Many contracts and projects do not even think about and SDLC.
They rarely add penetration testing and vulnerability testing in the development stages if at all
At best there is a bug bounty before the release of their main-nets
Which usually get hacked to hell and delayed because of it.
Things are getting better but they are still behind the curve, as the technology is new and blockchain mostly developers and marketers.Not hackers or security testers.
Forth Note:Potential Data Exposure via Future Broken Crypto
If sensitive data is placed on the blockchain it is there forever
Which means that if a cryptographic algorithm is broken anything which is encrypted with that algorithm is now accessible
We all know that algorithms are eventually broken!
So its always advisable to keep sensitive data hashed for integrity on the blockchain but not actually stored on the blockchain directly
Exploitation of Re-Entrancy Vulnerabilities:
With a bit of the background out of the way let's get into the first attack in this series.
Re-Entrancy attacks allow an attacker to create a re-cursive loop within a contract by having the contract call the target function rather than a single request from auser. Instead the request comes from the attackers contract which does not let the target contracts execution complete until the tasks intended by the attacker are complete. Usually this task will be draining the money out of the contract until all of the money for every user is in the attackers account.
Example Scenario:
Let's say that you are using a bank and you have deposited 100 dollars into your bank account.Now when you withdraw your money from your bank account the bank account first sends you 100 dollars before updating your account balance.
Well what if when you received your 100 dollars, it was sent to malicious code that called the withdraw function again not lettingthe initial target deduct your balance ?
With this scenario you could then request 100 dollars, then request 100 again and you now have 200 dollars sent to you from the bank. But 50% of that money is not yours. It's from the whole collection of money that the bank is tasked to maintain for its accounts.
Ok that's pretty cool, but what if that was in a re-cursive loop that did not BREAK until all accounts at the bank were empty?
That is Re-Entrancy in a nutshell.So let's look at some code.
Example Target Code:
function withdraw(uint withdrawAmount) public returns (uint) {
Line 1: Checks that you are only withdrawing the amount you have in your account or sends back an error.
Line 2: Sends your requested amount to the address the requested that withdrawal.
Line 3: Deducts the amount you withdrew from your account from your total balance.
Line 4. Simply returns your current balance.
Ok this all seems logical.. however the issue is in Line 2 - Line 3.The balance is being sent back to you before the balance is deducted. So if you were to call this from a piece of code which just accepts anything which is sent to it, but then re-calls the withdraw function you have a problem as it never gets to Line 3 which deducts the balance from your total. This means that Line 1 will always have enough money to keep withdrawing.
Let's take a look at how we would do that:
Example Attacking Code:
function attack() public payable {
1.bankAddress.withdraw(amount);
}
2.function () public payable {
3.if (address(bankAddress).balance >= amount) {
4.bankAddress.withdraw(amount);
}
}
Line 1: This function is calling the banks withdraw function with an amount less than the total in your account
Line 2: This second function is something called a fallback function. This function is used to accept payments that come into the contract when no function is specified. You will notice this function does not have a name but is set to payable.
Line 3:This line is checking that the target accounts balance is greater than the amount being withdrawn.
Line 4:Then again calling the withdraw function to continue the loop which will in turn be sent back to the fallback function and repeat lines over and over until the target contracts balance is less than the amount being requested.
Review the diagram above which shows the code paths between the target and attacking code. During this whole process the first code example from the withdraw function is only ever getting to lines 1-2 until the bank is drained of money. It never actually deducts your requested amount until the end when the full contract balance is lower then your withdraw amount. At this point it's too late and there is no money left in the contract.
Setting up a Lab Environment and coding your Attack:
Hopefully that all made sense. If you watch the videos associated with this blog you will see it all in action.We will now analyze code of a simple smart contract banking application. We will interface with this contract via our own smart contract we code manually and turn into an exploit to take advantage of the vulnerability.
Then lets open up an online ethereum development platform at the following link where we will begin analyzing and exploiting smart contracts in real time in the video below:
Coding your Exploit and Interfacing with a Contract Programmatically:
The rest of this blog will continue in the video below where we will manually code an interface to a full smart contract and write an exploit to take advantage of a Re-Entrency Vulnerability:
Conclusion:
In this smart contract exploit writing intro we showed a vulnerability that allowed for re entry to a contract in a recursive loop. We then manually created an exploit to take advantage of the vulnerability. This is just the beginning, as this series progresses you will see other types of vulnerabilities and have the ability to code and exploit them yourself. On this journey through the decentralized world you will learn how to code and craft exploits in solidity using various development environments and test nets.
Tor enables users to surf the Internet, chat and send instant messages anonymously, and is used by a wide variety of people for both Licit and Illicit purposes. Tor has, for example, been used by criminals enterprises, Hacktivism groups, and law enforcement agencies at cross purposes, sometimes simultaneously.
Nipe is a Script to make Tor Network your Default Gateway.
This Perl Script enables you to directly route all your traffic from your computer to the Tor Network through which you can surf the Internet Anonymously without having to worry about being tracked or traced back.
Download and install:
git clone https://github.com/GouveaHeitor/nipe cd nipe cpan install Switch JSON LWP::UserAgent
Commands:
COMMAND FUNCTION install Install dependencies start Start routing stop Stop routing restart Restart the Nipe process status See status
1) Do not connect to any public networks, anyone can sniff your data while you are on a public network.Evil Twin attack will be performed as a public network, so wherever possible restrict connecting to any open or public networks mainly if it wifi name is same as your wifi name
2) When your internet connection suddenly stops working, you might be under DOS attack using evil twin attack, just restart the router and the hacker need to restart the attack and as it takes some time. Maybe they leave it or continue some other time
3) Running a VPN to ensure that any browsing and transmitted data is done through an encrypted tunnel that cannot be easily snooped.
4) Do not always rely on the name of the network, make sure it is a legitimate and trusted network or not.
Wolfenstein Youngblood CODEX PC Game 2019 Overview
Wolfenstein: Youngblood is the first modern co-op Wolfenstein adventure. Nineteen years after the events of Wolfenstein II, BJ Blazkowicz has disappeared after a mission into Nazi-occupied Paris. Now, after years of training from their battle-hardened father, BJ's twin daughters, Jess and Soph Blazkowicz, are forced into action. Team up with a friend or play alone. Level up, explore, and complete missions to unlock new abilities, weapons, gadgets, cosmetics, and more to complement your playstyle and customize your appearance. Wolfenstein: Youngblood features the most open-ended Wolfenstein experience to date. From a new base of operations located deep in the heart of the Paris catacombs, plan how and when to attack and dismantle the Nazi regime.
Mature Content Description
The developers describe the content like this:
This is a first person shooter than contains Blood and Gore, Intense Violence, Strong Language, and Use of Drugs.
Technical Specifications of This Release.
Game Version : V1.0.3
Interface Language: English
Audio Language : English
Uploader / Re packer Group: Codex
Game File Name : Wolfenstein_Youngblood_Codex.iso
Game Download Size : 38 GB
MD5SUM : 723b36317fec0e02af0d507e0ebb9675
System Requirements of Wolfenstein Youngblood CODEX
Before you start Wolfenstein Youngblood CODEX Free Download make sure your PC meets minimum system requirements.
Minimum:
* Requires a 64-bit processor and operating system * OS: Win7, 8.1, or 10 (64-Bit versions) * Processor: AMD FX-8350/Ryzen 5 1400 or Intel Core i5-3570/i7-3770 * Memory: 8 GB RAM * Graphics: Nvidia GTX 770 4GB (Current available GPU GTX1650) or AMD equivalent * Storage: 40 GB available space
Recommended:
* Requires a 64-bit processor and operating system * OS: Win7, 8.1, or 10 64-Bit * Processor: AMD FX-9370/Ryzen 5 1600X or Intel Core i7-4770 * Memory: 16 GB RAM * Graphics: Nvidia GTX 1060 6GB (Current available GPU RTX2060) or AMD equivalent * Storage: 40 GB available space
Wolfenstein Youngblood CODEX Free Download
Click on the below button to start Wolfenstein Youngblood CODEX. It is full and complete game. Just download and start playing it. We have provided direct link full setup of the game.
Since I last posted about it, I've had the opportunity to play Apotheosis (the current title for my Worker Learning game) about a dozen times. We've quickly iterated on a couple of different aspects, going from 8 starting workers (one level 1 and one level 2 of each type) to 4 (one of each type, some level 1, some level 2, depending on turn order), adding a space to recruit more workers (I'm torn on this), adding a space to pay a chunk of resources for steps on the victory tracks, and tweaking the resolution of the Recall turns and the requirements and rewards for adventures.
The current version looks something like this:
You start with a Fighter, a Cleric, a Mage, and a Thief, 0/1/2/2 of them are level 2 at the beginning if you are player 1/2/3/4 (the ones that start leveled up are dealt to you randomly, and no two players will have the same combination of upgraded starting workers).
You take turns either placing a worker and gaining the benefit of that space (your worker must be at least tied for the highest level in that area), or recalling your workers and sending them on an adventure. Most spaces are better if you are higher level, or the right class. You can gain resources, train (level up), claim adventures (so nobody can do them out from under you), buy progress on the victory tracks, turn resources into blessings, which are like wild resources, visit the Throne Room to earn royal favors, or visit the tavern to recruit more workers.
When you place a worker, you have the opportunity to play a Side Quest card for either of 2 effects (one cares about what type of worker you are placing that turn, the other doesn't). When you recall workers, you earn steps on the three victory tracks, and if you qualify, you may do an adventure to earn more steps. The adventures have 3 tiers, and the higher the tier you do, the better the rewards. After returning from an adventure, your workers level up, becoming better at their jobs.
When you do certain Side Quests, or tier 3 adventures, you get a special resource called Spoils. You can visit the throne room to turn those Spoils into Royal Favors, which you can use at certain points on the victory tracks to take a "shortcut" as well as earn a Boon (reusable power card).
Design concerns
I'm noticing a real tightness in the design -- a difficulty creating adventures that are both doable by a player who has not recruited any new workers, but also doable by a player who has. The current level cap is 6, and so I wanted the adventures to require max 6 levels of any one class. If you hire a worker, then place it, and recall once, then you have 2 workers who's levels total 4 or 5 -- that's almost maxed out already! I am considering making the level cap 8 instead of 6, but d6s are easier to use in the prototype. Doing so would allow for more variety and more texture in the adventure requirements. It's also possible that not every adventure needs to be doable without recruiting another worker.
With just 4 types of worker, many of the tier 2 adventures require 3 of the 4 types. So you basically need to train up all of your workers if you wan to use them at all, there's not really such a things as choosing a class and neglecting it. I'm considering adding a 5th worker type to help with this -- it would allow the adventure requirements to be much more diverse.
Another thought is to add Split and/or Prestige classes: Split classes would be like regular workers, that count as either one or the other of two types (like a Fighter/Thief would count as either a Fighter or a Thief. Prestige classes would be like super workers that count as BOTH of two different types (Paladin = Fighter AND Cleric). For these you would probably have to discard your previous worker, therefore they BECOME a dual class worker.
Brainstorming possible solutions
Split/Prestige class workers would be pretty cool. but that sounds like expansion content to me. However adding a 5th (maybe even a 6th?) class to make the adventures more different from each other sounds reasonable. But that idea comes with its own challenges...
In the current game, each worker type is associated with 1 resource, and 3 of them are associated with one of the victory tracks. When you recall a fighter, you advance on the Crown Imperial track, and adventures that require fighters advance you further on that track. Thieves are associated with the Prince of Thieves track, and Mages are associated with the Mastermind track. Clerics are great supporting characters -- they aren't associated with any particular track, but instead give you Blessings, which are sort of like a wild resource that can be used in various different ways.
So if another worker type is added, do we need another resource? That might be a pain, but would be doable. Another victory track? I don't necessarily think that's a good idea (though I suppose it could work). What is another iconic adventurer class anyway?
One possibility is to make this 5th class a sort of Split/Prestige class like I mentioned above. Like a Paladin, which could act as either (or both) of a fighter or a cleric. But that would simply overload the fighter related stuff. So maybe better if whatever the new class is, it doesn't advance any of the tracks, but is otherwise "better" than a normal worker (counts as all types when placing?). Or perhaps it advances the track of your choice, and has some other drawback (doesn't count as any type when placing?).
As for the level caps, one way to fix that situation is to not use dice as workers (even though it's super convenient for prototypes). Instead, perhaps a mini or standee, with a base that has a little pointer, then a dial could be attached to the bottom such that the pointer points to the number on the tile corresponding to the current level. This is a user friendly way to not have to use dice, and therefore not be as limited in their value. The level cap could easily be 8, or even 9!
Another, different possible solution to the over-leveling issue is to limit the level-ups to only 1 per recall turn. This would slow things down considerably, and it would probably matter quite a bit which one you choose to gain levels and which ones you don't. It might also make a much bigger difference between playing 1-2 workers then recalling vs playing 3 or 4 before recalling. I'd be afraid this is TOO slow, but it ought to be easy enough to test. If it works, then that would make a level cap of 6 potentially viable after all.
