18th Annual Computer Security Applications Conference, 2002. Proceedings.
DOI: 10.1109/csac.2002.1176314
|View full text |Cite
|
Sign up to set email alerts
|

A toolkit for detecting and analyzing malicious software

Abstract: In this paper we present PEAT

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
16
0

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 26 publications
(16 citation statements)
references
References 6 publications
0
16
0
Order By: Relevance
“…At the semantically richer opcode level, Bilar [4] investigated and statistically compared opcode frequency distributions of malicious and non-malicious executables. Weber et al [54] start from the assumption that compiled binaries exhibit homogeneities with respect to several structural features such as instruction frequencies, instruction patterns, memory access, jumpcall distances, entropy metrics and byte-type probabilities and that tampering by malware would disturb these statistical homogeneities.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…At the semantically richer opcode level, Bilar [4] investigated and statistically compared opcode frequency distributions of malicious and non-malicious executables. Weber et al [54] start from the assumption that compiled binaries exhibit homogeneities with respect to several structural features such as instruction frequencies, instruction patterns, memory access, jumpcall distances, entropy metrics and byte-type probabilities and that tampering by malware would disturb these statistical homogeneities.…”
Section: Related Workmentioning
confidence: 99%
“…Analysis of non-graph-based structural features of executables were undertaken by [4,30,54]. Li et al [30] used statistical 1-g analysis of binary byte values to generate a fingerprint (a 'fileprint') for file type identification and classification purposes.…”
Section: Related Workmentioning
confidence: 99%
“…"the malicious code detection" [15], and the approach to determine whether malicious code has been inserted [16] to our model, in other words, the information is not used during training the model.…”
Section: Related Workmentioning
confidence: 99%
“…Another research aims to use the Windows Portable Executable (PE) file to determine whether malicious code has been inserted into an application after compilation [16].…”
Section: Related Workmentioning
confidence: 99%
“…Analysis of non-graph-based structural features of executables were undertaken by [4,30,54]. Li et al [30] used statistical 1-gram analysis of binary byte values to generate a fingerprint (a 'fileprint') for file type identification and classification purposes.…”
Section: (F)mentioning
confidence: 99%