TWI668592B - Method for automatically determining the malicious degree of Android App by using multiple dimensions - Google Patents
Method for automatically determining the malicious degree of Android App by using multiple dimensions Download PDFInfo
- Publication number
- TWI668592B TWI668592B TW106125420A TW106125420A TWI668592B TW I668592 B TWI668592 B TW I668592B TW 106125420 A TW106125420 A TW 106125420A TW 106125420 A TW106125420 A TW 106125420A TW I668592 B TWI668592 B TW I668592B
- Authority
- TW
- Taiwan
- Prior art keywords
- malicious
- detection
- behavior
- risk
- yes
- Prior art date
Links
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
本發明係揭露一種利用多維度自動判定Android App惡意程度的方法,利用二階段特徵值方式來檢測其靜態及動態行為是否含有風險,第一階段進行已知的黑白名單、病毒資訊、行為資訊等快速檢測,若無檢測出風險行為,則再進入第二階段的風險規則計算,結合使用權限、金鑰漏洞、動態行為偵測、嵌入的軟體開發工具包、敏感性風險、簡訊行為、隱私風險成為風險規則來進行風險分數的計算,以達到兼具快速檢測已知風險及探查可能未知風險的二項特點。 The invention discloses a method for automatically determining the malicious degree of an Android app by using multiple dimensions, and uses a two-stage eigenvalue method to detect whether the static and dynamic behaviors contain risks. In the first stage, a known black and white list, virus information, behavior information, etc. are performed. Rapid detection, if no risk behavior is detected, then enter the second phase of risk rule calculation, combined with permission, key vulnerability, dynamic behavior detection, embedded software development kit, sensitivity risk, SMS behavior, privacy risk Be a risk rule to calculate the risk score to achieve the two characteristics of quickly detecting known risks and exploring potentially unknown risks.
Description
本發明屬於一種利用多維度自動判定Android App惡意程度的方法,尤指一種針對於結合二階段特徵值的檢測方式。 The invention belongs to a method for automatically determining the malicious degree of an Android app by using multiple dimensions, in particular to a detection method for combining two-stage eigenvalues.
近年來,由於Android行動裝置作業系統的快速發展與大量用戶的使用,引起以往的電腦駭客注意並進行行動惡意程式的撰寫,其透過反組譯正常程式、嵌入惡意程式碼後再行封裝及發佈,即可以正常程式的外觀及功能,誘騙無知或不經意的使用者進行下載、安裝及運行,因而從中獲取非法利益及使用者個人資料;這些惡意程式可能散佈於各大論壇、雲端空間,甚至是Google Play官方商店。 In recent years, due to the rapid development of Android mobile device operating systems and the use of a large number of users, the previous computer hackers have noticed and written malicious programs. They have reversed the translation of normal programs, embedded malicious code and then packaged them. Release, that is, the appearance and function of the normal program, to deceive ignorant or casual users to download, install and run, thus obtaining illegal interests and user profiles; these malicious programs may be scattered in major forums, cloud space, and even Is the official Google Play store.
Android的惡意程式類型主要可分為加值服務濫用軟體、廣告軟體、資料竊取軟體、惡意破解軟體、點擊詐騙軟體、間諜程式等;一般而言,傳統的惡意程式偵測方式是採用已知的病毒碼偵測,或是採用反組譯程式碼的靜態分析、將程式運行於行動裝置或模擬器中再檢測其行為的動態分析,亦或是結合上述分析資料做一綜合判斷,然而目前行動裝置程式的數量呈現驚人的成長,為此分析系統只能不斷擴建軟硬體資源來處理此龐大的軟體成長量,加以駭客善於將惡意 程式碼藏匿於重新封裝後的正常程式中,影響了分析的成效,若是分析系統無法快速及有效解析出行動應用程式中的惡意行為,則無法及時偵測並保護行動裝置。 The malware types of Android can be mainly divided into value-added service abuse software, advertising software, data stealing software, malicious cracking software, click fraud software, spyware, etc. In general, the traditional malware detection method is known. Virus code detection, or static analysis using reverse-compiled code, dynamic analysis of running the program in a mobile device or simulator, and detecting the behavior of the program, or combining the above analysis data to make a comprehensive judgment, but the current action The number of device programs has grown tremendously. For this reason, the analysis system can only continuously expand the software and hardware resources to handle this huge amount of software growth, and the hacker is good at hiding malicious code in the re-packaged normal program, which affects The effectiveness of the analysis, if the analysis system can not quickly and effectively resolve the malicious behavior in the mobile application, it can not detect and protect the mobile device in time.
在公開編號TW 201426381 A的發明專利申請之惡意程式偵測方法與系統中,揭露了一種惡意程式的偵測方法,使用了靜態行為特徵及演算法進行偵測,但是此發明並未解決惡意程式於實際運作時才產生的惡意行為的問題,且頻繁出現於惡意程式之良性程式特徵容易混淆此類技術。 In the malware detection method and system of the invention patent application of the public number TW 201426381 A, a method for detecting a malicious program is disclosed, which uses static behavior features and algorithms for detection, but the invention does not solve the malicious program. The problem of malicious behavior that occurs during actual operation, and the benign program features that frequently appear in malicious programs can easily confuse such techniques.
在授權公開號CN 103354540 B的發明專利申請之一種android系統的惡意代碼檢測方法和裝置中,揭露了一種Android系統的惡意代碼檢測方法,透過監控系統中是否有簡訊攔截的現象,並使用簡訊內容比對程式中具有簡訊接收、讀取簡訊權限的位置來檢測其惡意行為,然而,此發明僅使用簡訊攔截機制作為偵測惡意程式的方法,並未考慮到惡意程式亦可能透過其他途徑,如網路進行資料傳輸。 In a method and device for detecting malicious code of an Android system of the invention patent application of the publication No. CN 103354540 B, a malicious code detection method of the Android system is disclosed, which detects whether there is a phenomenon of interception of the short message and uses the content of the short message through the monitoring system. The comparison program has a location for receiving and reading SMS messages to detect malicious behavior. However, the invention only uses the SMS interception mechanism as a method for detecting malicious programs, and does not consider that malicious programs may be through other channels, such as The network transmits data.
在公開編號TW I515598 B的發明專利申請之產生純化惡意程式的方法、偵測惡意程式之方法及其系統中,揭露了一種產生純化惡意程式的方法,使用複數資料流路徑來純化惡意程式,然而,此發明使用的僅有資料流相似度比對,並未使用到第三方的惡意程式資料庫加以強化其偵測效果。 In a method for generating a malicious program, a method for detecting a malicious program, and a system thereof for detecting a malicious program of the invention patent application number TW I515598 B, a method for generating a purified malicious program is disclosed, which uses a complex data stream path to purify a malicious program. This invention uses only the data stream similarity comparison, and does not use a third-party malware database to enhance its detection effect.
本案發明人鑑於上述習用方式所衍生的各項缺點,乃亟思加以改良創新,並經多年苦心孤詣潛心研究後,終於成功研發完成本利用多維度自動判定Android App惡意程度的方法。 In view of the shortcomings derived from the above-mentioned conventional methods, the inventor of the present invention has improved and innovated, and after years of painstaking research, he finally succeeded in researching and developing the method of automatically determining the malicious degree of the Android App by using multiple dimensions.
本發明之目的即在提出提供一種利用多維度自動判定Android App惡意程度的方法,除了提供比傳統動靜態檢測更加快速精準的效果之外,還適用於病毒檢測軟體無法檢測出的未知型態惡意程式,建立起一個獨特的二階段的檢測方法,以求快速檢測出行動惡意程式,並抑止其擴散速度及危害程度。 The object of the present invention is to provide a method for automatically determining the malicious degree of an Android App by using multiple dimensions. In addition to providing faster and more accurate effects than traditional dynamic and static detection, the present invention is also applicable to unknown malicious types that cannot be detected by virus detection software. The program establishes a unique two-stage detection method to quickly detect malicious programs and suppress the speed and harm.
為了達成上述發明目的之一種利用多維度自動判定Android App惡意程度的方法,使用了第一階段的快速檢測機制及第二階段的詳實檢測機制,係利用特徵分析系統所萃取出的行動應用程式特徵值來進行分析;每一個行動應用程式都可經由特徵分析系統取得其專有的特徵值,先依序進行第一階段的黑白名單、病毒資訊、行為資訊檢測,在階段過程中若任一檢測有顯示出風險,則立即進行回饋;使用者可自行維護黑白名單資訊、簽章資訊,並設定病毒資訊來源、比對機制,選擇欲判定的風險行為資訊;若第一階段無檢測出風險行為,則進入第二階段的詳實檢測;在檢測前會先給予預設的風險分數,第一步進行風險規則的比對,風險規則由使用權限、金鑰漏洞、動態行為偵測、嵌入的軟體開發工具包、敏感性風險、簡訊行為、隱私風險所組成,逐一比對多條風險規則並取相似度最高者,若相似度高於系統設定則判斷此行動應用程式符合此風險規則,並將提升風險分數,接續進行黑名單簽章、惡意網址的比對,若符合則提升分險分數,若不符合則降低風險分數,並輔以病毒偵測比率來增減分數,最終風險分數若是高於系統臨界值,則判定此行動應用程式為高度風險性;使用者也可自行維護風險規則,設定相似度範圍,增修黑名單簽章、惡意網址等。 In order to achieve the above-mentioned invention, a method for automatically determining the malicious degree of an Android app by using multiple dimensions uses a first-stage rapid detection mechanism and a second-stage detailed detection mechanism, which is a feature of the mobile application extracted by the feature analysis system. The value is used for analysis; each mobile application can obtain its own unique feature value through the feature analysis system, and firstly perform the first stage black and white list, virus information, behavior information detection, and if any detection in the phase process If there is a risk, the feedback will be provided immediately; the user can maintain the black and white list information, the signature information, and set the virus information source and comparison mechanism to select the risk behavior information to be determined; if the risk behavior is not detected in the first stage , enter the second stage of detailed testing; prior to testing will give the default risk score, the first step is to compare the risk rules, risk rules by use rights, key vulnerabilities, dynamic behavior detection, embedded software Development kit, sensitivity risk, SMS behavior, privacy risk, one by one The risk rule is the highest similarity. If the similarity is higher than the system setting, the mobile application is judged to meet the risk rule, and the risk score will be upgraded. The blacklist signature and the malicious website will be compared. The risk score, if not met, reduces the risk score and supplements the virus detection rate to increase or decrease the score. If the final risk score is higher than the system threshold, the mobile application is determined to be highly risky; the user can also Maintain risk rules, set similarity ranges, add blacklist signatures, malicious URLs, etc.
一種利用多維度自動判定Android App惡意程度的方法,其步驟包括:步驟一、選定待檢測的行動應用程式;步驟二、利用特徵分析進行App的特徵值萃取,以取出靜動態行為特徵;步驟三、存入App特徵值資料庫;步驟四、進行第一階段的快速檢測,並迅速判斷是否符合已知的特徵值檢測;步驟五、若為是,則判定為惡意程式;步驟六、若為否,則進行第二階段的詳實檢測,並計算風險值是否高於臨界值;步驟七、若為是,則判定為惡意程式;以及步驟八、若為否,則判定為非惡意程式。 A method for automatically determining the malicious degree of an Android app by using multiple dimensions, the steps comprising: Step 1: Selecting an action application to be detected; Step 2, using feature analysis to extract feature values of the App to extract static and dynamic behavior features; Step 3 And stored in the App feature value database; Step 4, perform the first stage of rapid detection, and quickly determine whether the known feature value detection is met; Step 5, if yes, determine as a malicious program; Step 6 if Otherwise, the second stage of detailed detection is performed, and whether the risk value is higher than the critical value is calculated; if the answer is yes, it is determined to be a malicious program; and if it is no, it is determined to be a non-malicious program.
其中步驟四之第一階段的快速檢測,其流程包括:步驟一、取得待檢測的行動應用程式特徵值;步驟二、判斷檢測是否為黑名單,若為是,則判定為惡意程式;步驟三、若為否,則判斷檢測是否為白名單,若為是,則判定為非惡意程式;步驟四、若為否,則判斷檢測是否為病毒資訊,若為是,則判定為惡意程式;步驟五、若為否,則判斷是否通過行為檢測,若為是,則判定為惡意程式;以及步驟六、若為否,則需進行第二階段的詳實檢測。 The first step of the fourth step of the rapid detection, the process includes: step one, obtain the action application feature value to be detected; step two, determine whether the test is a blacklist, if yes, determine the malicious program; step three If yes, it is determined whether the detection is a white list. If yes, it is determined to be a non-malicious program; if the determination is yes, the determination is whether the detection is a virus information, and if yes, the determination is a malicious program; 5. If no, it is judged whether the behavior is detected. If it is, it is determined to be a malicious program; and if it is no, if it is no, the second stage of detailed detection is required.
其中步驟四之病毒資訊,包含病毒廠商、病毒名稱、或是數量大於系統設定的臨界值,其步驟五之行為檢測,其中 行為包含取得最高管理者權限之行為、提昇權限之行為、金鑰洩漏之行為。 The virus information in step 4 includes the virus manufacturer, the virus name, or the threshold value greater than the threshold set by the system, and the behavior detection of step 5, wherein the behavior includes the behavior of obtaining the highest administrator authority, the behavior of improving the authority, and the key leakage. Behavior.
因此,從App特徵資料庫取得待檢測行動應用程式的特徵值;至已知惡意行為資料庫取得行動應用程式的黑名單並進行比對動作,若是該行動應用程式為黑名單,則立即判定為惡意程式,不需要做後續的比對動作;已知惡意行為資料庫取得行動應用程式的白名單並進行比對動作,若是行動應用程式為白名單,則立即判定為非惡意程式,不需要做後續的比對動作;已知惡意行為資料庫取得行動應用程式的病毒掃描結果並進行比對動作,若是該行動應用程式的病毒掃描結果有掃描出系統所設定的病毒廠商、病毒名稱、或是數量大於系統設定的臨界值,則立即判定為惡意程式,不需要做後續的比對動作;App特徵資料庫取得該行動應用程式的特徵值並進行比對動作,若是該行動應用程式的特徵值符合取得最高管理者權限的行為、提昇權限的行為、金鑰洩漏的行為以上任一行為,則立即判定為惡意程式,不需要做後續的比對動作,若是該行動應用程式皆無符合的行為,則須繼續後續的第二階段的檢測動作;以及將上述檢測步驟相關資訊儲存於風險結果資料庫。 Therefore, the feature value of the mobile application to be detected is obtained from the App signature database; the known malicious behavior database is used to obtain the blacklist of the mobile application and the comparison action is performed; if the mobile application is blacklisted, it is immediately determined as The malicious program does not need to perform subsequent comparison actions; the malicious behavior database is known to obtain the white list of the mobile application and perform the comparison action. If the mobile application is whitelisted, it is immediately determined to be a non-malicious program, and does not need to be done. Subsequent comparison actions; the malicious behavior database is known to obtain the virus scan result of the mobile application and perform the comparison action. If the virus scan result of the mobile application scans the virus manufacturer, the virus name, or If the number is greater than the threshold set by the system, it is immediately determined to be a malicious program, and no subsequent comparison action is required; the App signature database obtains the feature value of the mobile application and performs a comparison action, and if it is the feature value of the mobile application Compliance with the behavior of obtaining the highest administrator authority, the act of promoting the authority, and the leakage of the key For any of the above behaviors, it is immediately determined to be a malicious program, and no subsequent comparison action is required. If the mobile application has no matching behavior, the subsequent second stage detection action must be continued; and the detection steps are related. Information is stored in the risk results database.
其中步驟六之第二階段的詳實檢測,其流程包括:步驟一、取得待測的行動應用程式特徵值,並給予一預設的風險分數;步驟二、判斷風險規則比對,相似度是否最高,若為是,則增加風險分數,若為否,則減低風險分數;步驟三、判斷檢測是否為黑名單簽章,若為是,則增加風險分數,若為否,則減低風險分數; 步驟四、判斷檢測是否為惡意網址,若為是,則增加風險分數,若為否,則減低風險分數;步驟五、進行病毒檢測;以及步驟六、判斷風險分數是否高於系統臨界值,若為是,則判定為惡意程式,若為否,則判定為非惡意程式。 The detailed detection of the second stage of step 6 includes the following steps: Step 1: Obtain the characteristic value of the action application to be tested, and give a predetermined risk score; Step 2: Determine the risk rule comparison, whether the similarity is the highest If yes, increase the risk score. If not, reduce the risk score. Step 3: Determine whether the test is a blacklist signature. If yes, increase the risk score. If not, decrease the risk score. 4. Determine whether the detection is a malicious website. If yes, increase the risk score. If not, reduce the risk score; Step 5, conduct virus detection; and Step 6. Determine whether the risk score is higher than the system threshold. Yes, it is determined to be a malicious program, and if not, it is determined to be a non-malicious program.
因此,從App特徵資料庫取得待檢測行動應用程式的特徵值,並給予一個初始的風險分數供後續使用;風險規則資料庫取得所有的風險規則,並逐條比對行動應用程式特徵值與其相似程度,最終取得相似度最高的規則,並將風險分數加上此規則的相似度分數,若是相似度程度低於系統臨界值,則進行減低風險分數動作;已知惡意行為資料庫取得黑名單簽章資訊並進行比對動作,若是該行動應用程式的簽章特徵值符合,則提升風險分數,若是該行動應用程式無符合的簽章特徵值,則進行減低風險分數動作;已知惡意行為資料庫取得惡意網址並進行比對動作,若是該行動應用程式的網址特徵值符合,則提升風險分數,若是該行動應用程式無符合的網址特徵值,則將進行減低風險分數動作;已知惡意行為資料庫取得行動應用程式的病毒掃描結果並進行比對動作,並依據病毒偵測比例的提升分險分數;進行風險分數的判斷,若是風險分數高系統臨界值,則判定為惡意程式,若否則判定為非惡意程式;以及將最後檢測結果儲存於風險結果資料庫。 Therefore, the feature value of the mobile application to be detected is obtained from the App signature database, and an initial risk score is given for subsequent use; the risk rule database obtains all risk rules and compares the action application feature values one by one. Degree, the rule with the highest similarity is finally obtained, and the risk score is added to the similarity score of the rule. If the degree of similarity is lower than the system threshold, the risk score action is performed; the malicious behavior database is known to obtain the blacklist sign. Chapter information and comparison actions, if the signature value of the mobile application is consistent, the risk score is increased, and if the mobile application does not have the signature signature value, the risk reduction action is performed; the malicious behavior data is known. The library obtains the malicious URL and compares the action. If the mobile application's URL feature value matches, the risk score is increased. If the mobile application does not match the URL feature value, the risk score action is performed; the malicious behavior is known. The database obtains the virus scan results of the mobile application and compares them According to the virus detection ratio of the increase in the risk score; the risk score is judged, if the risk score is high, the system is judged to be a malicious program, if otherwise determined to be non-malicious; and the final test result is stored in the risk Results database.
本發明所提供一種利用多維度自動判定Android App惡意程度的方法,與其他習用技術相互比較時,更具備下列優點: The invention provides a method for automatically determining the malicious degree of an Android app by using multiple dimensions, and has the following advantages when compared with other conventional technologies:
1. 本發明可快速且精確的達到自動判定Android App惡意程度的目的,利用多維度的檢測方式,可進行 快速檢測及詳實檢測二種方式,若是面對大量的檢測需求亦無需花費高成本來建置軟硬體設備。 1. The invention can quickly and accurately achieve the purpose of automatically determining the malicious degree of the Android App, and utilizes the multi-dimensional detection method to perform two methods of rapid detection and detailed detection, and does not need to cost a high cost if faced with a large number of detection requirements. Establish software and hardware devices.
2. 本發明提供風險規則比對的功能。利用使用權限、金鑰漏洞、動態行為偵測、嵌入的軟體開發工具包、敏感性風險、簡訊行為、隱私風險所組成的風險規則為基礎,來判別行動裝置程式的特徵值較為符合的風險規則來進行判斷,達到可檢測出未知型態惡意程式的效果。 2. The present invention provides the function of risk rule comparison. Based on risk rules consisting of usage rights, key vulnerabilities, dynamic behavior detection, embedded software development kits, sensitivity risks, newsletter behaviors, and privacy risks, the risk rules for determining the eigenvalues of mobile device programs are determined. To judge, to achieve the effect of detecting unknown malware.
3. 本發明可建立於企業內外部的Android App檢測機制,充分提升行動裝置使用的安全性。可藉由介接企業進入端口的網路系統,達到阻斷惡意程式進入企業的路徑,若是建立於外部則可對使用者提供上傳樣本及檢測結果,以達到擴充樣本數以增加風險規則數量並提升檢測效果。 3. The invention can be built on the Android App detection mechanism inside and outside the enterprise to fully improve the security of the mobile device. The network system that enters the port of the enterprise can be used to block the path of the malicious program entering the enterprise. If it is established externally, the user can be provided with the uploaded sample and the detection result, so as to increase the number of samples to increase the number of risk rules and improve the number of risk rules. Detect the effect.
S110~S151‧‧‧流程 S110~S151‧‧‧ Process
S210~S260‧‧‧第一階段的快速檢測流程 S210~S260‧‧‧The first stage of the rapid detection process
S310~S362‧‧‧第二階段的詳實檢測流程 S310~S362‧‧‧The second phase of the detailed inspection process
請參閱有關本發明之詳細說明及其附圖,將可進一步瞭解本發明之技術內容及其目的功效;有關附圖為:圖1為本發明利用多維度自動判定Android App惡意程度的方法之流程圖;圖2為本發明利用多維度自動判定Android App惡意程度的方法之第一階段的快速檢測流程圖;圖3為本發明利用多維度自動判定Android App惡意程度的方法之第二階段的詳實檢測流程圖。 The detailed description of the present invention and its accompanying drawings will be further understood, and the technical contents of the present invention and the functions thereof can be further understood. FIG. 1 is a flow chart of the method for automatically determining the malicious degree of an Android App by using multiple dimensions. FIG. 2 is a flow chart of the first stage of the method for automatically determining the malicious degree of the Android App by using multiple dimensions; FIG. 3 is a detailed view of the second stage of the method for automatically determining the malicious degree of the Android app by using multiple dimensions. Test flow chart.
為了使本發明的目的、技術方案及優點更加清楚 明白,下面結合附圖及實施例,對本發明進行進一步詳細說明。應當理解,此處所描述的具體實施例僅用以解釋本發明,但並不用於限定本發明。 The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
以下,結合附圖對本發明進一步說明:請參閱圖1所示,為本發明利用多維度自動判定Android App惡意程度的方法之流程圖,其步驟包括:步驟一、S110選定待檢測的行動應用程式;步驟二、S120利用特徵分析進行App的特徵值萃取,以取出靜動態行為特徵;步驟三、S130存入App特徵值資料庫;步驟四、S140進行第一階段的快速檢測,並迅速判斷是否符合已知的特徵值檢測;步驟五、若為是,則S141判定為惡意程式;步驟六、若為否,則S150進行第二階段的詳實檢測,並計算風險值是否高於臨界值;步驟七、若為是,則S141判定為惡意程式;以及步驟八、若為否,則S151判定為非惡意程式。 The present invention is further described with reference to the accompanying drawings. Referring to FIG. 1 , a flowchart of a method for automatically determining the malicious degree of an Android app by using multiple dimensions is provided. The steps include: Step 1 and S110: Selecting a mobile application to be detected. Step 2: S120 uses feature analysis to extract the feature values of the App to extract the static and dynamic behavior features; Step 3: S130 is stored in the App feature value database; Step 4: S140 performs the first phase of the rapid detection, and quickly determines whether Corresponding to the known feature value detection; step 5, if yes, then S141 is determined to be a malicious program; step 6 if not, then S150 performs detailed detection of the second phase, and calculates whether the risk value is higher than the critical value; 7. If yes, S141 determines that it is a malicious program; and if it is no, step S151 determines that it is a non-malicious program.
依上述流程得知,由調度伺服器從待檢測樣本中選出欲派送的檢測樣本,並將其派送至特徵分析系統進行檢測,特徵分析系統進行檢測樣本的分析過程,過程中包含了靜態分析及動態分析,並可解析出來此樣本的特徵值,其特徵值包含了雜湊值、簽章、使用的權限、連線網址、動態行為偵測、嵌入軟體開發工作包、敏感性風險、簡訊行為、隱私暴露風險、是否有取得最高管理者權限的行為、是否有提昇權限的行為、是否有金鑰洩漏的行為等。特徵分析系統將所檢測出來的特徵資料儲存於App特徵資料庫,以利於後續的檢測機制所使 用,接著進行第一階段的快速檢測機制,使用目前已知的特徵值檢測來判斷是否為惡意程式,再依據結果進行第二階段的快速檢測機制,使用分險分數來判斷是否為惡意程式,若是經第一或二階段檢測完成為惡意程式的風險結果,則儲存至風險結果資料庫。 According to the above process, the dispatching server selects the test sample to be sent from the sample to be detected, and sends it to the feature analysis system for detection. The feature analysis system performs the analysis process of the test sample, and the process includes static analysis and Dynamic analysis, and can parse the eigenvalues of this sample. Its eigenvalues include hash values, signatures, permissions used, connection URLs, dynamic behavior detection, embedded software development work packages, sensitivity risks, SMS behaviors, The risk of privacy exposure, whether there is an act of obtaining the highest administrator's authority, whether there is an act of escalating authority, and whether there is a key leak. The feature analysis system stores the detected feature data in the App feature database for use by the subsequent detection mechanism, and then performs the first phase of the rapid detection mechanism, using the currently known feature value detection to determine whether it is a malicious program. According to the result, the second stage of the rapid detection mechanism is used, and the risk score is used to determine whether it is a malicious program. If the risk result of the malware is completed by the first or second stage detection, it is stored in the risk result database.
其中上述步驟四之第一階段的快速檢測,請參閱圖2所示,為本發明利用多維度自動判定Android App惡意程度的方法之第一階段的快速檢測流程圖,其流程包括:步驟一、S210取得待檢測的行動應用程式特徵值;步驟二、S220判斷檢測是否為黑名單,若為是,則S221判定為惡意程式;步驟三、若為否,則S230判斷檢測是否為白名單,若為是,則S231判定為非惡意程式;步驟四、若為否,則S240判斷檢測是否為病毒資訊,若為是,則S221判定為惡意程式;步驟五、若為否,則S250判斷是否通過行為檢測,若為是,則S221判定為惡意程式;以及步驟六、若為否,則需S260進行第二階段的詳實檢測。 The fast detection of the first stage of the foregoing step 4 is as shown in FIG. 2 , which is a fast detection flowchart of the first stage of the method for automatically determining the malicious degree of the Android app by using multiple dimensions, and the process includes: Step 1: S210 obtains the action application feature value to be detected; in step 2, S220 determines whether the detection is a blacklist, and if so, S221 determines that it is a malicious program; and step 3, if not, then S230 determines whether the detection is a white list, if If yes, S231 determines that it is a non-malicious program; if the answer is no, then S240 determines whether the detection is virus information, and if so, S221 determines that it is a malicious program; and if the answer is NO, step S250 determines whether it is passed. Behavior detection, if yes, S221 is determined to be a malicious program; and if it is no, step S26 is required to perform the second phase of detailed detection.
其中步驟四之病毒資訊,包含病毒廠商、病毒名稱、或是數量大於系統設定的臨界值,其步驟五之行為檢測,其中行為包含取得最高管理者權限之行為、提昇權限之行為、金鑰洩漏之行為。 The virus information in step 4 includes the virus manufacturer, the virus name, or the threshold value greater than the threshold set by the system, and the behavior detection of step 5, wherein the behavior includes the behavior of obtaining the highest administrator authority, the behavior of improving the authority, and the key leakage. Behavior.
因此,綜合上述流程得知,第一階段分析伺服器從App特徵資料庫取得待檢測行動應用程式的特徵值以利於後續進行比對動作,至已知惡意行為資料庫取得行動應用程式的黑名單並進行比對動作,若是該行動應用程式為黑名單,則 立即判定為惡意程式,不需要做後續的比對動作,若是該行動應用程式非黑名單,則須繼續後續的比對動作,已知惡意行為資料庫取得行動應用程式的白名單並進行比對動作,若是該行動應用程式為白名單,則立即判定為非惡意程式,不需要做後續的比對動作,若是該行動應用程式非白名單,則須繼續後續的比對動作,接著至已知惡意行為資料庫取得行動應用程式的病毒掃描結果並進行比對動作,若是該行動應用程式的病毒掃描結果有掃描出系統所設定的病毒廠商、病毒名稱、或是數量大於系統設定的臨界值,則立即判定為惡意程式,不需要做後續的比對動作,若是該行動應用程式不符合上述設定值,則須繼續後續的比對動作,至App特徵資料庫取得該行動應用程式的特徵值並進行比對動作,若是該行動應用程式的特徵值符合取得最高管理者權限的行為、提昇權限的行為、金鑰洩漏的行為以上任一行為,則立即判定為惡意程式,不需要做後續的比對動作,若是該行動應用程式皆無符合的行為,則須繼續後續的第二階段的檢測動作,在第一階段分析伺服器中的檢測步驟中,若是判斷為惡意程式會將資訊儲存於風險結果資料庫中。 Therefore, according to the above process, the first-stage analysis server obtains the feature value of the mobile application to be detected from the App feature database to facilitate subsequent comparison operations, and obtains a blacklist of the mobile application from the known malicious behavior database. And the comparison action is performed. If the mobile application is blacklisted, it is immediately determined to be a malicious program, and no subsequent comparison action is required. If the mobile application is not blacklisted, the subsequent comparison action must be continued. Knowing the malicious behavior database to obtain the white list of the mobile application and performing the comparison action. If the mobile application is whitelisted, it is immediately determined to be a non-malicious program, and no subsequent comparison action is required. If the mobile application is not For the whitelist, the subsequent comparison action must be continued. Then, the known malicious behavior database is used to obtain the virus scan result of the mobile application and the comparison action is performed. If the virus scan result of the mobile application is scanned, the system sets the scan result. If the virus manufacturer, virus name, or quantity is greater than the threshold set by the system, it is immediately determined to be The malicious program does not need to perform subsequent comparison actions. If the mobile application does not meet the above set value, the subsequent comparison action must be continued, and the feature data of the mobile application is obtained from the App feature database and the comparison action is performed. If the behavior value of the mobile application conforms to any behavior of obtaining the highest administrator authority, the behavior of promoting the authority, and the behavior of the key leakage, it is immediately determined to be a malicious program, and no subsequent comparison action is required. If the mobile application has no conforming behavior, it must continue the subsequent second phase of the detection. In the detection step in the first phase analysis server, if it is determined that the malicious program stores the information in the risk result database.
判定Android App惡意程度的方法之流程中步驟六之第二階段的詳實檢測,請參閱圖3所示,為本發明利用多維度自動判定Android App惡意程度的方法之第二階段的詳實檢測流程圖,其流程包括:步驟一、S310取得待測的行動應用程式特徵值,並給予一預設的風險分數;步驟二、S320判斷風險規則比對,相似度是否最高,若為是,則S321增加風險分數,若為否,則S322 減低風險分數;步驟三、S330判斷檢測是否為黑名單簽章,若為是,則S331增加風險分數,若為否,則S332減低風險分數;步驟四、S340判斷檢測是否為惡意網址,若為是,則S341增加風險分數,若為否,則S342減低風險分數;步驟五、S350進行病毒檢測;以及步驟六、S360判斷風險分數是否高於系統臨界值,若為是,則S361判定為惡意程式,若為否,則S362判定為非惡意程式。 For detailed detection of the second stage of step 6 in the process of determining the malicious degree of the Android App, please refer to FIG. 3, which is a detailed detection flowchart of the second stage of the method for automatically determining the malicious degree of the Android App by using multiple dimensions. The process includes: Step 1: S310 obtains the action application feature value to be tested, and gives a preset risk score; Step 2: S320 determines the risk rule comparison, whether the similarity is the highest, and if yes, the S321 is increased. Risk score, if not, then S322 reduces the risk score; Step 3, S330 determines whether the test is a blacklist signature, if yes, then S331 increases the risk score, if not, then S332 reduces the risk score; Step 4, S340 Determine whether the detection is a malicious website. If yes, S341 increases the risk score. If not, then S342 reduces the risk score; Step 5, S350 performs virus detection; and Step 6 and S360 determines whether the risk score is higher than the system threshold. If YES, S361 determines that it is a malicious program, and if not, S362 determines that it is a non-malicious program.
依上述流程得知,第二階段分析伺服器從App特徵資料庫取得待檢測行動應用程式的特徵值以利於後續進行比對動作,並給予一個初始的風險分數供後續使用,接著在風險規則資料庫取得所有的風險規則,並逐條比對行動應用程式特徵值與其相似程度,最終取得相似度最高的規則,並將風險分數加上此規則的相似度分數,若是相似度程度低於系統臨界值,則進行減低風險分數動作,在已知惡意行為資料庫取得黑名單簽章資訊並進行比對動作,若是該行動應用程式的簽章特徵值符合,則提升風險分數,若是該行動應用程式無符合的簽章特徵值,則進行減低風險分數動作,至已知惡意行為資料庫取得惡意網址並進行比對動作,若是該行動應用程式的網址特徵值符合,則提升風險分數,若是該行動應用程式無符合的網址特徵值,則將進行減低風險分數動作,在已知惡意行為資料庫取得行動應用程式的病毒掃描結果並進行比對動作,並依據病毒偵測比例的提升分險分數,最終在進行風險分數的判斷,若是風險分數高系統臨界值,則判定為惡意程式, 若否則判定為非惡意程式,並將最後檢測結果儲存於風險結果資料庫。 According to the above process, the second-stage analysis server obtains the feature value of the action application to be detected from the App feature database to facilitate subsequent comparison actions, and gives an initial risk score for subsequent use, and then in the risk rule data. The library obtains all the risk rules and compares the action application eigenvalues with their similarity one by one, and finally obtains the rule with the highest similarity, and adds the risk score to the similarity score of the rule. If the degree of similarity is lower than the system criticality Value, the risk reduction action is performed, the blacklist signature information is obtained in the known malicious behavior database and the comparison action is performed, and if the signature signature value of the mobile application is consistent, the risk score is raised, and if the action application is If there is no matching signature feature value, the risk score reduction action is performed, and the malicious malicious database is obtained to obtain a malicious website and the comparison action is performed. If the behavioral value of the mobile application is consistent, the risk score is raised, and if the action is If the app does not match the URL feature value, the risk score action will be reduced. Obtaining the virus scan result of the mobile application in the known malicious behavior database and performing the comparison action, and based on the virus detection ratio, the risk score is finally determined, and if the risk score is high, the threshold value is If it is determined to be a malicious program, otherwise it is determined to be a non-malicious program, and the final detection result is stored in the risk result database.
上列詳細說明乃針對本發明之一可行實施例進行具體說明,惟該實施例並非用以限制本發明之專利範圍,凡未脫離本發明技藝精神所為之等效實施或變更,均應包含於本案之專利範圍中。 The detailed description of the present invention is intended to be illustrative of a preferred embodiment of the invention, and is not intended to limit the scope of the invention. The patent scope of this case.
綜上所述,本案不僅於技術思想上確屬創新,並具備習用之傳統方法所不及之上述多項功效,已充分符合新穎性及進步性之法定發明專利要件,爰依法提出申請,懇請 貴局核准本件發明專利申請案,以勵發明,至感德便。 To sum up, this case is not only innovative in terms of technical thinking, but also has many of the above-mentioned functions that are not in the traditional methods of the past. It has fully complied with the statutory invention patent requirements of novelty and progressiveness, and applied for it according to law. Approved this invention patent application, in order to invent invention, to the sense of virtue.
Claims (5)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW106125420A TWI668592B (en) | 2017-07-28 | 2017-07-28 | Method for automatically determining the malicious degree of Android App by using multiple dimensions |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW106125420A TWI668592B (en) | 2017-07-28 | 2017-07-28 | Method for automatically determining the malicious degree of Android App by using multiple dimensions |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| TW201911102A TW201911102A (en) | 2019-03-16 |
| TWI668592B true TWI668592B (en) | 2019-08-11 |
Family
ID=66590118
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| TW106125420A TWI668592B (en) | 2017-07-28 | 2017-07-28 | Method for automatically determining the malicious degree of Android App by using multiple dimensions |
Country Status (1)
| Country | Link |
|---|---|
| TW (1) | TWI668592B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020261425A1 (en) * | 2019-06-26 | 2020-12-30 | 楽天株式会社 | Fraud deduction system, fraud deduction method, and program |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103440458A (en) * | 2013-09-25 | 2013-12-11 | 西安交通大学 | Method for statically identifying malicious codes of Android system in heuristic manner |
| TW201537379A (en) * | 2014-03-17 | 2015-10-01 | Chunghwa Telecom Co Ltd | Computer program product and method for information safety monitoring and defense |
| CN106557695A (en) * | 2015-09-25 | 2017-04-05 | 卓望数码技术(深圳)有限公司 | A kind of malicious application detection method and system |
| US9661009B1 (en) * | 2014-06-26 | 2017-05-23 | Fireeye, Inc. | Network-based malware detection |
| CN106845217A (en) * | 2017-01-20 | 2017-06-13 | 四川中大云科科技有限公司 | A kind of detection method of Android application malicious act |
| TW201721497A (en) * | 2015-12-08 | 2017-06-16 | 英希羅有限公司 | Systems and methods for detection of malicious code in runtime generated code |
| US9690936B1 (en) * | 2013-09-30 | 2017-06-27 | Fireeye, Inc. | Multistage system and method for analyzing obfuscated content for malware |
-
2017
- 2017-07-28 TW TW106125420A patent/TWI668592B/en not_active IP Right Cessation
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103440458A (en) * | 2013-09-25 | 2013-12-11 | 西安交通大学 | Method for statically identifying malicious codes of Android system in heuristic manner |
| US9690936B1 (en) * | 2013-09-30 | 2017-06-27 | Fireeye, Inc. | Multistage system and method for analyzing obfuscated content for malware |
| TW201537379A (en) * | 2014-03-17 | 2015-10-01 | Chunghwa Telecom Co Ltd | Computer program product and method for information safety monitoring and defense |
| US9661009B1 (en) * | 2014-06-26 | 2017-05-23 | Fireeye, Inc. | Network-based malware detection |
| CN106557695A (en) * | 2015-09-25 | 2017-04-05 | 卓望数码技术(深圳)有限公司 | A kind of malicious application detection method and system |
| TW201721497A (en) * | 2015-12-08 | 2017-06-16 | 英希羅有限公司 | Systems and methods for detection of malicious code in runtime generated code |
| CN106845217A (en) * | 2017-01-20 | 2017-06-13 | 四川中大云科科技有限公司 | A kind of detection method of Android application malicious act |
Also Published As
| Publication number | Publication date |
|---|---|
| TW201911102A (en) | 2019-03-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Abawajy et al. | Identifying cyber threats to mobile-IoT applications in edge computing paradigm | |
| Elish et al. | Profiling user-trigger dependence for Android malware detection | |
| US8479296B2 (en) | System and method for detecting unknown malware | |
| US10986103B2 (en) | Signal tokens indicative of malware | |
| US9336389B1 (en) | Rapid malware inspection of mobile applications | |
| US9798981B2 (en) | Determining malware based on signal tokens | |
| CN108280350B (en) | Android-oriented mobile network terminal malicious software multi-feature detection method | |
| KR101720686B1 (en) | Apparaus and method for detecting malcious application based on visualization similarity | |
| TWI461953B (en) | Computing environment security method and electronic computing system | |
| CN102882875B (en) | Active defense method and device | |
| US20120272322A1 (en) | Determining the vulnerability of computer software applications to privilege-escalation attacks | |
| Wang et al. | Uncovering and exploiting hidden apis in mobile super apps | |
| Suarez-Tangil et al. | Thwarting obfuscated malware via differential fault analysis | |
| Bhuiyan et al. | API vulnerabilities: Current status and dependencies | |
| CN105404816A (en) | Content-based vulnerability detection method and device | |
| Faruki et al. | Droidolytics: robust feature signature for repackaged android apps on official and third party android markets | |
| CN106919844B (en) | A kind of android system vulnerability of application program detection method | |
| TWI668592B (en) | Method for automatically determining the malicious degree of Android App by using multiple dimensions | |
| Short et al. | Android smartphone third party advertising library data leak analysis | |
| CN103942494B (en) | Method and system for auditing malicious software | |
| Alhashmi et al. | Mobile and web applications clones: A comprehensive study | |
| Tien et al. | MAS: mobile-apps assessment and analysis system | |
| Han et al. | Context awareness through reasoning on private analysis for Android application | |
| Rizvi et al. | A hybrid framework for detecting repackaged applications on the android market | |
| CN107358101A (en) | It is a kind of that software detecting method and system are extorted based on permission mode |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| MM4A | Annulment or lapse of patent due to non-payment of fees |