http://blog.marcocantu.com/. It's as good a primer as any in terms of getting rid of it and staving it off in the future.
Checkpoints ...  THIS version of the virus only affects programmers working in Delphi 5 through 7.  The non-radical solution is to search your system for SysConst.DCU and look at it/them in Notepad. There will be obvious code that jumps to code at the end.  The infected files will be 18K in size, rather than 12K in size.  Delete the infected files  copy the SysConst.BAK in the LIB sub-folder of where D7 is installed to SysConst.DCU, but DO NOT DELETE that BAK file. Induc.A looks for that file and decides you are already infected, if something infected comes along your way again. Mind you, that protection doesn't necessarily mean Induc.B will work that way, but every little bit of cure helps.  You have to basically recompile (Build-CtrlF2) any project you compiled subsequent to being infected.
The guts of this infection vector is to infect programmer's pre-built compiled code. Then, any new programs/updates from that programmer carries the virus. That's why some narrow niche apps written in Delphi are infected and on the loose, as are a number of general programs that were written in Delphi and released to the public. There are some very well-known apps that were released in the last few days that have the virus.
Naturally, we've now been forewarned about this 'not' new infection vector. Ken Thompson famously posited it years ago. Embarcadero is working on a solution to help we few atavists that cling to Delphi 7. But all programmers, Delphi, Rails, Python, VB and .NET alike, have now been warned to take more stringent measures to protect our programming environment. The next version of Induc won't be so benign.
That's why I'm not sleeping at nights.