Behavioral analysis for identification of malicious code
Techniques are described for a behavioral analysis of metadata associated with source code to identify malicious source code. For example, this disclosure describes a computing system configured to obtain metadata associated with source code of a software package. The computing system is also configured to determine, based on the metadata associated with source code, whether there are any anomalies associated with the source code. The computing system is further configured to, in response to determining that there is at least one anomaly associated with the source code, compute a score for the software package. The computing system is also configured to perform an action based on the score for the software package.
1. A method comprising:
obtaining, by a computing system, metadata associated with source code of a software package;
determining, by the computing system and based on the metadata associated with source code, whether there are any anomalies associated with the source code;
in response to determining that there is at least one anomaly associated with the source code, computing, by the computing system, an overall risk level for the software package, wherein computing the overall risk level for the software package is based on an author risk score that specifies a value that indicates a risk level of behavior of the author, a popularity score that specifies a value that indicates the popularity of the software package, and a health score that specifies a value that indicates a health of the software package; and
performing, by the computing system, an action based on the overall risk level for the software package, wherein performing the action comprises blocking use of the software package in a software product.
2. The method of claim 1 , wherein determining whether there are any anomalies associated with the source code comprises:
determining whether there are any anomalies associated with the source code based on behavior of an author of the source code.
3. The method of claim 2 , wherein determining whether there are any anomalies associated with the source code based on behavior of an author of the source code comprises:
determining whether there are any anomalies associated with one or more actions performed by the author of the source code associated with a commit of the source code.
4. The method of claim 2 , wherein determining whether there are any anomalies associated with the source code based on behavior of an author of the source code comprises:
determining whether there are any anomalies associated with the source code based on a time a commit of the source code occurred.
5. The method of claim 2 , wherein determining whether there are any anomalies associated with the source code based on behavior of an author of the source code comprises:
determining whether the author of the source code committed one or more lines of source code for a plurality of software packages.
6. The method of claim 2 , wherein determining whether there are any anomalies associated with the source code based on behavior of an author of the source code comprises:
determining whether a commit of the source code was unsigned from the author who typically signs.
7. The method of claim 1 , wherein performing the action comprises outputting, by the computing system and to an administrator computing device, an indication that the software package has at least one anomaly associated with the source code.
8. The method of claim 1 , wherein obtaining metadata associated with source code of the software package comprises:
obtaining metadata associated with source code from one or more of a source code repository or software package manager.
9. A computing system comprising:
a memory; and
one or more processors in communication with the memory, the one or more processors configured to:
obtain metadata associated with source code of a software package;
determine, based on the metadata associated with source code, whether there are any anomalies associated with the source code;
in response to determining that there is at least one anomaly associated with the source code, compute an overall risk level for the software package, wherein computing the overall risk level for the software package is based on an author risk score that specifies a value that indicates a risk level of behavior of the author, a popularity score that specifies a value that indicates the popularity of the software package, and a health score that specifies a value that indicates a health of the software package; and
perform an action based on the overall risk level for the software package, wherein performing the action comprises blocking use of the software package in a software product.
10. The computing system of claim 9 , wherein to determine whether there are any anomalies associated with the source code, the one or more processors are configured to:
determine whether there are any anomalies associated with the source code based on behavior of an author of the source code.
11. The computing system of claim 10 , wherein to determine whether there are any anomalies associated with the source code based on behavior of an author of the source code, the one or more processors are configured to:
determine whether there are any anomalies associated with one or more actions performed by the author of the source code associated with a commit of the source code.
12. The computing system of claim 10 , wherein to determine whether there are any anomalies associated with the source code based on behavior of an author of the source code, the one or more processors are configured to:
determine whether there are any anomalies associated with the source code based on a time a commit of the source code occurred.
13. The computing system of claim 10 , wherein to determine whether there are any anomalies associated with the source code based on behavior of an author of the source code, the one or more processors are further configured to:
determine whether the author of the source code committed one or more lines of source code for a plurality of software packages.
14. The computing system of claim 10 , wherein to determine whether there are any anomalies associated with the source code based on behavior of an author of the source code, the one or more processors are further configured to:
determine whether a commit of the source code was unsigned from the author who typically signs.
15. The computing system of claim 9 , wherein to perform the action, the one or more processors are configured to:
output, to an administrator computing device, an indication that the software package has at least one anomaly associated with the source code.
16. Non-transitory computer-readable storage media comprising instructions that, when executed, cause one or more processors to:
obtain metadata associated with source code of a software package;
determine, based on the metadata associated with source code, whether there are any anomalies associated with the source code;
in response to determining that there is at least one anomaly associated with the source code, compute an overall risk level for the software package, wherein computing the overall risk level for the software package is based on an author risk score that specifies a value that indicates a risk level of behavior of the author, a popularity score that specifies a value that indicates the popularity of the software package, and a health score that specifies a value that indicates a health of the software package; and
perform an action based on the overall risk level for the software package, wherein performing the action comprises blocking use of the software package in a software product.