Browse State-of-the-Art › Obfuscation Detection

Obfuscation Detection

1 paper with code · 0 benchmarks · 0 datasets archive 2025-07-28

Benchmarks archive 2025-07-28

No benchmark for this task in the archive.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

No dataset record in the archive lists this task.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Papers archive 2025-07-28

archive papers tagged: 3 · with a code link: 1 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran: none of the 3 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 3 of 3, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.

  • 1 Jan 2019 1 repository listed
    This is typically applied to protect intellectual property in benign apps, or to hinder the process of extracting actionable information in the case malware.
  • Identifying Obfuscated Code through Graph-Based Semantic Analysis of Binary Code
    2 Apr 2025 0 repositories listed
    Protecting sensitive program content is a critical issue in various situations, ranging from legitimate use cases to unethical contexts.
  • Command-line Obfuscation Detection using Small Language Models
    5 Aug 2024 0 repositories listed
    To avoid detection, adversaries often use command-line obfuscation.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections