Skip to content
This repository was archived by the owner on Nov 27, 2020. It is now read-only.

Commit

Permalink
Minor changes
Browse files Browse the repository at this point in the history
 - Changed TabIndexes
 - Updated README and LICENSE
  • Loading branch information
Strappazzon committed Feb 27, 2019
1 parent b6b9ddf commit 22343e5
Show file tree
Hide file tree
Showing 7 changed files with 19 additions and 16 deletions.
Binary file added .github/images/file_permissions.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .github/images/syskey.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .github/images/syskey_demo.gif
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion LICENSE
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
MIT License

Copyright (c) 2018 Alberto Strappazzon
Copyright (c) 2019 Alberto Strappazzon

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
Expand Down
13 changes: 8 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,11 @@
# SCAM Lock Tool
![SCAM Lock Tool](https://puu.sh/BnTGm.png)

This is a fake SAM Lock Tool (known as syskey). Scammers use it to lock their victims out of their computers, encrypting the credentials stored inside the SAM file with a password. This version is virtually identical to the original syskey, the only difference is that scammers won't be able to encrypt SAM.
![SCAM Lock Tool](.github/images/syskey.png)

This is a fake SAM Lock Tool (also known as syskey). Scammers use it to lock their victims out of their computer, encrypting the credentials stored inside the SAM file with a password. This version is virtually identical to the original syskey, the only difference is that scammers won't be able to encrypt SAM.

## How to replace syskey

Replacing a system file is not as easy as a copy and paste, you need to take ownership over the file. To do so:
- Go to `C:\Windows\System32\` and right click `syskey.exe`
- Click **Properties**, open the **Security** tab, click the **Advanced** button, then open the **Owner** tab
Expand All @@ -16,11 +18,12 @@ Replacing a system file is not as easy as a copy and paste, you need to take own
- Now tick the box next to **Full Control** and click **OK** until you close all the dialogs
- Windows will ask you: "*You are about to change the permission settings on system folders* [...] *Do you want to continue?*", confirm with **Yes**

![File Permissions](https://puu.sh/BnUcQ.png)
![File Permissions](.github/images/file_permissions.png)

Now you can rename **syskey.exe** in **syskey.exe.bak** to make a backup. At this point all you have to do is paste my syskey.exe inside system32.

## Preview
You can see the fake syskey in action below. An higher quality video is available [here on puush](https://puu.sh/By2sw.mp4).

![SCAM Lock Tool Preview](https://puu.sh/By2SK.gif)
You can see this fake syskey in action below.

![SCAM Lock Tool Preview](.github/images/syskey_demo.gif)
2 changes: 1 addition & 1 deletion SCAM Lock Tool/My Project/AssemblyInfo.vb
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,6 @@ Imports System.Runtime.InteropServices
' by using the '*' as shown below:
' <Assembly: AssemblyVersion("1.0.*")>

<Assembly: AssemblyVersion("1.0.0.0")>
<Assembly: AssemblyVersion("1.0.1.0")>
<Assembly: AssemblyFileVersion("6.1.7600.16385")>
<Assembly: NeutralResourcesLanguage("en-US")>
18 changes: 9 additions & 9 deletions SCAM Lock Tool/startupKey.Designer.vb

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit 22343e5

Please sign in to comment.