Source code repair method for malicious code detection

A data processing computer system for repairing infected source code prior to performing a code build, the infected source code including a first component and other components containing dependencies to the first component comprising:

• code management library system including:
• a memory;
• a processor;
• a detection module for detecting a virus pattern in the first component of the source code;
• a identification module for identifying the other components in the source code containing the dependencies to the first component;
• a retraction module for only retracting the first component and the identified other components from a current code build;
• a replacement module for replacing the first component and the identified other components with a prior version of the first component and prior versions of the identified other components from an archive of a previous code build;
• and
• a build module for performing the current code build of the source code using the prior version of the first component and the prior versions of the identified other components, wherein
• the identification module includes rules defined from relationships between the first component and the other components in the source code.

A computer-readable tangible storage medium having stored thereon a computer program for repairing infected source code prior to performing a code build, the infected source code including a first component and other components containing dependencies to the first component, the computer program comprising a routine set of instructions for causing a data processing system to perform the steps of:

• detecting a virus pattern in the first component of the infected source code;
• responsive to the detecting of the virus pattern, identifying the other components in the source code containing the dependencies to the first component;
• only retracting the first component and the identified other components from a current code build;
• replacing the first component and the identified other components with a prior version of the first component and prior versions of the identified other components from an archive of a previous code build;
• and
• performing the current code build of the source code using the prior version of the first component and the prior versions of the identified other components, wherein
• the identifying step is based on rules defined from relationships between the first component and the other components in the source code.