Jump to content

[GR]Πως να "Χακάρετε" το Gmail, Facebook με τη χρήση του Backtrack 5


Recommended Posts

Αρχικά ανοίξτε μία γραμμή εντολών (shell) στο backtrack και πληκτρολογήστε

την παρακάτω εντολή για να ελέγξετε την ip σας.

42706764.jpg

 

Τώρα ξανά ανοίξτε μία γραμμή εντολών (shell) στο backtrack και πληκτρολογήστε

την παρακάτω εντολή:

 

cd /pentest/exploits/set

 

και μετά δώστε:

 

./set

 

για να ανοίξει το εργαλείο Set.

 

77387563.jpg

 

Έπειτα επιλέξτε την επιλογή 2, “Website Attack Vectors”.

 

95077054.jpg

 

Σε αυτό το σημείο θα επιλέξουμε την επιλογή 4 “Tabnabbing Attack Method”.

 

25009014.jpg

 

Στη συνέχεια διαλέγουμε την επιλογή 2 “Site Cloner”.

 

73629290.jpg

 

Τώρα πληκτρολογήστε την διεύθυνση από το site που θέλετε να κλωνοποιήσετε, εδώ για το παράδειγμά μας διαλέχαμε http://www.gmail.com και πατήστε το enter.

Το SET θα κλωνοποιήσει το web site και πατήστε το return για να συνεχίσετε.

 

83983454.jpg

 

Κατόπιν μετατρέψτε την URL σε Google URL χρησιμοποιώντας το goo.gl και στείλτε το τελικό link στο "θύμα" με email, chat ή ότι άλλο θέλετε.

 

44448497.jpg

 

Τέλος, όταν το "θύμα" το ανοίξει θα δεί το μήνυμα ότι η σελίδα φορτώνει ακόμη. Έτσι το "θύμα" θα προσπαθήσει να ανοίξει καινούργια καρτέλα στον browser του.

Μόλις γίνει αυτό, αμέσως το ψεύτικο website μας θα αρχίσει να δουλεύει. Αυτό θα ανακατευθύνει το "θύμα" στην phising σελίδα μας και έτσι θα μπορέσουμε να του πάρουμε τα

στοιχεία πρόσβασής του.

 

gmails.jpg

 

hackjn.jpg

 

***Απευθήνετε για άτομα που είναι στο ίδιο δίκτυο

Credits: Hackhosting.com

Link to comment
Share on other sites

Ωραιος οδηγος φιλε μου!Καλο θα ειναι να γνωριζεις καποια πραγματα για αυτα που δημοσιευεις ομως!Και μπραβο που δινεις τα credits εκει που ανηκουν!

Link to comment
Share on other sites

  • 4 weeks later...
  • 6 months later...
  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



  • Posts

    • I guess if you want to learn the whole process, your best bet is to start with a classic client (like salvation? also must be easy to modify so that you don't get stuck behind paywalls) and check how the network communication is implemented. L2jmobius has a lot of sources that use classic clients.
    • DISCORD : utchiha_market telegram : https://t.me/utchiha_market SELLIX STORE : https://utchihamkt.mysellix.io/ Join our server for more products : https://discord.gg/hoodservices https://campsite.bio/utchihaamkt  
    • WTS Gold bars reborn interlude x10   discord : xeenthekeen
    • Guys, if you'd let me be the bearer of bad news, No amount of "break from server development" can justify your complete lack of idea how things work. If it was this easy, you should've been seeing 90% of the servers of the popular old versions, such as IL and HF, running on the newest client. For this task, you would need a lot of time - think at least 2 months, if you can code, have access to all the necessary tools for client development, and you have a relatively good idea of how server<->client communication works. f you don't, then you either find yourself a well-paying job and find someone who would do it for you or you put the idea aside (for no less than 1-2 years) and start reading and learning asap. Let me give you a little preview/breakdown of what some of the work includes. The work can be split into two parts - SERVER side and CLIENT side.  The server and the client communicate through packets. Each of these packets has a defined structure. Both, the server and the client MUST know this structure and MUST use the same structure, otherwise they won't be able to "understand" each other. - The server side predominantly includes the alteration of existing packet structure and the creation (from zero) of missing packets that the client requires. Then you also have to take these changes into account and alter the existing features of your server to match the changes. A good example for this is SKILL ENCHANTING. On older chronicles, the enchant level is determined by the LEVEL value of the skill and on the new clients, it has been taken out into a separate value. What this means is that you would have to figure out a way to adapt the old system to the new requirements. - Now that we mentioned the client, you would also need to edit a bunch of files, such as Interface, UTX, UNR, as well as DAT files, including those related to ITEMS, SKILLS, QUESTS, NPCS, and AUGMENTATION STATS and DESCRIPTIONS, etc. For some of those, you would also have to figure out how to check for missing entries and how to parse data from the older client to the new. The best example, again, would be the SKILLS. On the latest clients, the skill enchanting was limited to only +20. As such, even if there were some matching skills between the two different client versions, you would still need to add the missing 10 levels to +30. And once you complete all of that, you start testing and fixing bugs and sh1t. And once you have fixed all of that, you can start adding new features from the new client, because otherwise it would be one big mess and a waste of time and/or money.
  • Topics

×
×
  • Create New...