False Filename Extension Detection for Multi-Extension Attack Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional methods fail to accurately and efficiently detect multi-extension attacks, where malicious files are disguised with innocuous-looking filenames, leading to potential execution on computing devices.

Innovation Solution

Systems and methods that detect potentially malicious files by identifying suspicious combinations of characters within filenames, specifically false filename extensions in the middle section, preventing execution and comparing filenames to malware signatures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional file detection methods are used, then device complexity remains low, but detection precision fails to identify multi-extension attacks

Engineering Contradiction:
Improvedetection precisionVSAvoiddevice complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The filename analysis is segmented into multiple sections (middle section and end section) to identify false extensions. The system divides the detection process into distinct phases: scanning for suspicious character combinations in the middle section, verifying against known extension patterns, and cross-referencing with malware signatures, thereby achieving precise detection without requiring complex full-file analysis

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary detection of false filename extensions before file execution. By analyzing the filename structure in advance and identifying suspicious patterns (such as unexpected extension sequences), the system prevents malicious files from being executed, maintaining low computational overhead while improving detection accuracy

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If file execution is allowed without verification, then ease of operation is high, but harmful factors increase due to undetected malicious files

Engineering Contradiction:
Improveease of operationVSAvoidharmful factors
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system introduces an intermediary filename analysis mechanism that operates between file download and execution. This intermediary layer checks filename patterns for suspicious characteristics (such as multiple extensions or unusual character combinations) without requiring full file execution or content analysis, thereby maintaining ease of operation while blocking harmful files

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system applies preliminary anti-action by preemptively identifying and blocking files with suspicious filename patterns before they can execute harmful code. By detecting false extensions and comparing against malware signatures in advance, the system neutralizes potential threats without affecting legitimate file operations, thus reducing harmful factors while preserving user convenience

Inventive Principle:
Principle #9Preliminary anti-action

3Measurement precision

If comprehensive file analysis is performed, then detection precision improves, but productivity decreases due to execution delays

Engineering Contradiction:
Improvedetection precisionVSAvoidproductivity
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The system applies partial action by performing only the necessary filename pattern matching and extension verification without conducting comprehensive file content analysis. By focusing detection efforts on the filename structure (checking for false extensions and suspicious patterns) rather than analyzing the entire file, the system achieves sufficient detection precision while minimizing execution delays and maintaining productivity

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10116688B1Systems and methods for detecting potentially malicious files
Publication Date: 2018.10.30 CA TECH INC
  • US10116688B1 patent drawing
  • US10116688B1 patent drawing
  • US10116688B1 patent drawing

AI summary

The disclosed computer-implemented method for detecting potentially malicious files may include (1) detecting an attempt by the computing device to execute a file, (2) prior to execution of the file, determining that a filename of the file contains a combination of characters indicative of a false filename extension included within a middle section of the filename, (3) determining, based at least in part on the false filename extension being included within the middle section of the filename, that the file is potentially malicious, and then in response to determining that the file is potentially malicious, (4) preventing the computing device from executing the file. Various other methods, systems, and computer-readable media are also disclosed.