2012
DOI: 10.1080/19393555.2011.624160
|View full text |Cite
|
Sign up to set email alerts
|

Analysis and Identification of Malicious JavaScript Code

Abstract: Malicious JavaScript code has been actively and recently utilized as a vehicle for Web-based security attacks. By exploiting vulnerabilities such as cross-site scripting (XSS), attackers are able to spread worms, conduct Phishing attacks, and do Web page redirection to "typically" porn Web sites. These attacks can be preemptively prevented if the malicious code is detected before executing. Based on the fact that a malignant code will exhibit certain features, we propose a novel classification-based detection … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2014
2014
2024
2024

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 11 publications
(8 citation statements)
references
References 7 publications
0
8
0
Order By: Relevance
“…Keeping in view the impact that an attack can cause on the client side, detection of JavaScript at a real time thus became necessary. Several approaches have been proposed for classification and detection of malicious JavaScript code from the benign code of a website such as those of Rieck et al [5], Curtsinger et al [6], and Fraiwan et al [7], the problem of these approaches is time overhead in detection. Other approaches such as GATEKEEPER [8] and Google Caga [9] use a method of executing random JavaScripts from the code in a protected environment but can detect the limited type of attacks.…”
Section: Introductionmentioning
confidence: 99%
“…Keeping in view the impact that an attack can cause on the client side, detection of JavaScript at a real time thus became necessary. Several approaches have been proposed for classification and detection of malicious JavaScript code from the benign code of a website such as those of Rieck et al [5], Curtsinger et al [6], and Fraiwan et al [7], the problem of these approaches is time overhead in detection. Other approaches such as GATEKEEPER [8] and Google Caga [9] use a method of executing random JavaScripts from the code in a protected environment but can detect the limited type of attacks.…”
Section: Introductionmentioning
confidence: 99%
“…(6) The Background Script displays the result to the user. (7) Extending our approach in order to detect malware written in other programming languages, such as VBScript, Java, C, and C++. Because there is no need for us to manually craft features, the work flow for detecting malicious code written in other languages would be similar with that in our paper.…”
Section: Conclusion and Discussionmentioning
confidence: 99%
“…Many researches concerned about the particular attack types, such as drive-by downloads [2,12] and heap spraying [13], relied on recognizing specific attacks. In addition to these methods, some tools have been developed for analyzing JavaScript code [7][8][9]14]. Although these approaches are effective and reduce the threat of attacks to a certain degree, they can hardly detect the evolving JavaScript attacks and often consume a large amount of time analyzing JavaScript code.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations