Browser Plugin Malicious Manipulation Detection via CSP Violation Feedback

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Content Security Policy (CSP) techniques fail to effectively notify users of malicious script injections and manipulations by plugins or extensions in browser applications, allowing users to unknowingly continue using compromised applications.

Innovation Solution

A data processing system that includes a processor and memory, which receives a request for web application content, transmits content source rules, analyzes rule violation reports for malicious modifications, and sends user alerts to the user device, including a unique web application user ID, to notify users of potential malicious modifications and risks across associated devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If Content Security Policy (CSP) is implemented to block malicious scripts, then script execution security is improved, but user notification capability is lost

Engineering Contradiction:
Improvescript execution securityVSAvoiduser notification capability
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system implements feedback by monitoring CSP violations and plugin manipulations, then notifying users through alerts. The server receives violation reports from the browser, analyzes them to detect malicious activity, and sends notifications back to the user device, creating a closed-loop feedback mechanism that informs users of security incidents without compromising CSP enforcement

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The server acts as an intermediary between the browser's CSP enforcement mechanism and the user. It receives violation reports from the browser, performs analysis to determine malicious modifications, and transmits notifications to the user device. This intermediary role allows the system to maintain CSP security while adding user notification capability that CSP alone cannot provide

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If CSP blocks DOM manipulations by plugins, then web page security is improved, but user awareness of malicious plugins is reduced

Engineering Contradiction:
Improveweb page securityVSAvoiduser awareness of malicious plugins
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system provides feedback to users about plugin manipulations by monitoring DOM changes and sending notifications when malicious plugins are detected. The server receives manipulation reports, analyzes them to confirm malicious intent, and notifies users, enabling them to be aware of and take action against malicious plugins while the CSP continues to block their operations

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The server serves as an intermediary that bridges the gap between CSP's automated blocking mechanism and user awareness. It collects information about plugin manipulations from the browser, performs analysis to distinguish benign from malicious activity, and communicates findings to users, thereby maintaining both security enforcement and user knowledge

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If browser applications allow plugin extensions, then functionality and adaptability are improved, but vulnerability to malicious code increases

Engineering Contradiction:
Improveplugin functionalityVSAvoidmalicious code injection
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system implements feedback by continuously monitoring plugin behavior and notifying users when malicious activity is detected. The server receives reports of attempted manipulations, analyzes them to determine malicious intent, and sends alerts to users, enabling the system to maintain plugin functionality while providing real-time security awareness and allowing users to respond to threats

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary action by proactively monitoring and analyzing plugin behavior before malicious code can fully execute harmful operations. By detecting violation reports and analyzing them in real-time, the system can identify and notify users about potential threats early, enabling preventive user action before complete compromise occurs

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3830726B1Content policy based notification of application users about malicious browser plugins
Publication Date: 2024.05.22 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3830726B1 patent drawingFigure 1
  • EP3830726B1 patent drawingFigure 2A
  • EP3830726B1 patent drawingFigure 2B

AI summary

Disclosed systems and methods include receiving, by a browser application, a web application data including a trusted source rule having a web application user identifier (ID) unique to a user of the web application, and upon determining by the browser application of a violation of the trusted source rule, transmitting a rule violation report, with the web application user ID, to a data processing system for analysis to determine a malicious manipulation of the browser application, and receiving at the user device, from the data processing system, an alert of malicious manipulation of the browser application, corresponding to the rule violation report.