Topic
Opcode
About: Opcode is a research topic. Over the lifetime, 1048 publications have been published within this topic receiving 14794 citations. The topic is also known as: operation code & OPCODE.
Papers published on a yearly basis
Papers
22 Mar 2017
TL;DR: A novel android malware detection system that uses a deep convolutional neural network (CNN) to perform static analysis of the raw opcode sequence from a disassembled program, removing the need for hand-engineered malware features.
Abstract: In this paper, we propose a novel android malware detection system that uses a deep convolutional neural network (CNN). Malware classification is performed based on static analysis of the raw opcode sequence from a disassembled program. Features indicative of malware are automatically learned by the network from the raw opcode sequence thus removing the need for hand-engineered malware features. The training pipeline of our proposed system is much simpler than existing n-gram based malware detection methods, as the network is trained end-to-end to jointly learn appropriate features and to perform classification, thus removing the need to explicitly enumerate millions of n-grams during training. The network design also allows the use of long n-gram like features, not computationally feasible with existing methods. Once trained, the network can be efficiently executed on a GPU, allowing a very large number of files to be scanned quickly.
533 citations
TL;DR: This paper proposes a new method to detect unknown malware families based on the frequency of the appearance of opcode sequences, and describes a technique to mine the relevance of each opcode and assess the Frequency of Each opcode sequence.
447 citations
TL;DR: A framework for detecting new malicious code in executable files can be designed to achieve very high accuracy while maintaining low false positives (i.e. misclassifying benign files as malicious) and should include training of multiple classifiers on various types of features, as well as an active learning mechanism to maintain high detection accuracy.
365 citations
TL;DR: This supplement to Interactive Music Systems contains audio and program examples that document a variety of systems and the music they produce.
Abstract: From the Publisher:
This supplement to Interactive Music Systems contains audio and program examples that document a variety of systems and the music they produce. An extensive library of Macintosh software allows the user to experiment with or adapt existing interactive systems. Some parts of the library require the presence of underlying software environments, such as SrnallTalk, LISP, or Opcode's Max Language. The program discussed most extensively on interactive music systems, Robert Rowe's Cypher, will run on any Macintosh computer.
286 citations
22 Jun 2003
TL;DR: The closer analysis of the propagation patterns indicates that it is feasible to identify strategic locations for embedding additional assertions in the source code of a given subsystem to detect errors and, hence, to prevent propagation.
Abstract: This paper describes an experimental study of Linux kernel behavior in the presence of errors that impact the instruction stream of the kernel code. Extensive error injection experiments including over 35,000 errors are conducted targeting the most fre- quently used functions in the selected kernel subsystems. Three types of faults/errors injection campaigns are conducted: (1) ran- dom non-branch instruction, (2) random conditional branch, and (3) valid but incorrect branch. The analysis of the obtained data shows: (i) 95% of the crashes are due to four major causes, namely, unable to handle kernel NULL pointer, unable to handle kernel paging request, invalid opcode, and general protection fault, (ii) less than 10% of the crashes are associated with fault propagation and nearly 40% of crash latencies are within 10 cycles, (iii) errors in the kernel can result in crashes that require reformatting the file system to restore system operation; the process of bringing up the system can take nearly an hour. Subsequently, over 35,000 faults/errors are injected into the kernel functions within four subsystems: architecture- dependent code (arch), virtual file system interface (fs), cen- tral section of the kernel (kernel), and memory management (mm). Three types of fault/error injection campaigns are con- ducted: random non-branch, random conditional branch, and valid but incorrect conditional branch. The data is analyzed to quantify the response of the OS as a whole based on the sub- system and to determine which functions are responsible for error sensitivity. The analysis provides a detailed insight into the OS behavior under faults/errors. The major findings in- clude: • Most crashes (95%) are due to four major causes: unable to handle kernel NULL pointer, unable to handle kernel paging request, invalid opcode, and general protection fault. • Nine errors in the kernel result in crashes (most severe crash category), which require reformatting the file system. The process of bringing up the system can take nearly an hour. • Less than 10% of the crashes are associated with fault propagation, and nearly 40% of crash latencies are within 10 cycles. The closer analysis of the propagation patterns indicates that it is feasible to identify strategic locations for embedding additional assertions in the source code of a given subsystem to detect errors and, hence, to prevent er- ror propagation.
227 citations
Related Topics (5)
Performance Metrics
| Year | Papers |
|---|---|
| 2025 | 16 |
| 2024 | 48 |
| 2023 | 51 |
| 2022 | 86 |
| 2021 | 54 |
| 2020 | 91 |