게임 정보
Welcome to The //HEX demo.
So you've decided to ditch the straight and narrow, and try your hand at hacking?
Well, it just so happens that we have the perfect job for a noob like you.
The Central bank of Bech is currently busy switching over to a new IT service provider, which means that this is the perfect time to execute a cyber attack.
You have a small window of opportunity, so you'll have to be quick, and keep your wits about you.
This bank contains two security measurement flaws; namely the Injection and Force nodes, leaving 2 open vulnerabilities for you to bypass in order to withdraw the recommended funds to your account.
Your role as //HACKER consists of the following:
//INJECTION NODE
Connect a path from our output to the target machine's input ports in order for control to inject the SQL code.
You will have to rotate pieces and inform your //CONTROL where the missing pieces are that they need to fill.
After which you have connected all the pipes with no visible 'leaks' that may cause data loss, you may inform your //CONTROL that they may initiate the attack.
//FORCE NODE
Use your brute force skills to pass in possible passwords into the login's password input.
Wait for further instructions from your //CONTROL whom is calculating the probability of each password.
When the correct password has been revealed you may continue with the final step.
//TRANSFER
Here you should start the Revenue Transfer Protocol (RTP), where the available funds in the bank will be transferred to your account.
But don't sit back and watch the cash role in just yet, as some of the portpipes will be traced.
If a portpipe gets traced while there is data flowing through, it will cause the pipe to be closed and essentially 'break', making the pipe useless for the rest of the RTP.
You'll have to listen to your //CONTROL to know which pipes need to be manually closed before the trace has begun.
Await on your //CONTROL to inform you when the RTP needs to be stopped to not pass the detection threshold.
Your role as //CONTROL consists of the following:
//INJECTION NODE
Await instructions from your //HACKER in which location they require a connection piece in order to establish a valid connection.
After which you have to inject the SQL commands.
//FORCE NODE
Every time your //HACKER tries to input a possible password, you will receive a packet containing the password along with a probability percentage.
The packet can be calculated to retrieve a list of passwords containing the correct letters in reference of the packet's password.
On receiving a high probability chance the list of passwords should be small enough for the //HACKER to Brute Force the login.
//TRANSFER
Once the //HACKER has initiated the RTP, you will be notified on white portpipes will be traced.
Your job is to inform the //HACKER which pipes they need to close to not get traced.
You are as well responsible for informing them when to stop the RTP as it nears the threshold.
So you've decided to ditch the straight and narrow, and try your hand at hacking?
Well, it just so happens that we have the perfect job for a noob like you.
The Central bank of Bech is currently busy switching over to a new IT service provider, which means that this is the perfect time to execute a cyber attack.
You have a small window of opportunity, so you'll have to be quick, and keep your wits about you.
This bank contains two security measurement flaws; namely the Injection and Force nodes, leaving 2 open vulnerabilities for you to bypass in order to withdraw the recommended funds to your account.
Your role as //HACKER consists of the following:
//INJECTION NODE
Connect a path from our output to the target machine's input ports in order for control to inject the SQL code.
You will have to rotate pieces and inform your //CONTROL where the missing pieces are that they need to fill.
After which you have connected all the pipes with no visible 'leaks' that may cause data loss, you may inform your //CONTROL that they may initiate the attack.
//FORCE NODE
Use your brute force skills to pass in possible passwords into the login's password input.
Wait for further instructions from your //CONTROL whom is calculating the probability of each password.
When the correct password has been revealed you may continue with the final step.
//TRANSFER
Here you should start the Revenue Transfer Protocol (RTP), where the available funds in the bank will be transferred to your account.
But don't sit back and watch the cash role in just yet, as some of the portpipes will be traced.
If a portpipe gets traced while there is data flowing through, it will cause the pipe to be closed and essentially 'break', making the pipe useless for the rest of the RTP.
You'll have to listen to your //CONTROL to know which pipes need to be manually closed before the trace has begun.
Await on your //CONTROL to inform you when the RTP needs to be stopped to not pass the detection threshold.
Your role as //CONTROL consists of the following:
//INJECTION NODE
Await instructions from your //HACKER in which location they require a connection piece in order to establish a valid connection.
After which you have to inject the SQL commands.
//FORCE NODE
Every time your //HACKER tries to input a possible password, you will receive a packet containing the password along with a probability percentage.
The packet can be calculated to retrieve a list of passwords containing the correct letters in reference of the packet's password.
On receiving a high probability chance the list of passwords should be small enough for the //HACKER to Brute Force the login.
//TRANSFER
Once the //HACKER has initiated the RTP, you will be notified on white portpipes will be traced.
Your job is to inform the //HACKER which pipes they need to close to not get traced.
You are as well responsible for informing them when to stop the RTP as it nears the threshold.
