Ollydbg, commonly called OD, is a common tool for disassembly. I love to crack OD's own 1 18 shell script and various plug-ins, which are very powerful and basically do not need to install other plug-ins. The window characteristics of OD are changed to avoid targeted detection. The shortcut key of OD window is changed to TAB key, the additional window is changed to support scrolling, the plug-in is loaded first when OD is started, and the string plug-in released by cold air in the forum night is also changed. Effectively solved the BUG of string exit and added the advancedolly plug-in, effectively solved the BUG that OD can't be modified in batches and the data window with shell can't follow up. Changed the class name of OD child window, updated some plug-ins and added some plug-ins. Sod is set to select all by default, and will update itself to solve the problem in the future. When the code is injected, the security guard in prompt box 360 may falsely report that the driver released by StrongOD is a virus, resulting in some functions being unavailable during the debugging of ollydbg. I want to remind you here to avoid misunderstanding. If there are no obstacles in the debugging process, I hope that everyone will temporarily shield the 360 security guards during the debugging process.