Website Runtime Security Testing for Malicious Script Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing website vulnerability detection methods, particularly static analysis, fail to identify malicious third-party scripts that have been secretly injected into trusted libraries, leading to potential security threats that go undetected.

Innovation Solution

A system for automated, real-time client-side testing of websites using dynamic analysis and event-based rules to identify security vulnerabilities, including monitoring for plain text encoding and third-party account data exfiltration, and simulating user interactions to detect malicious scripts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If static analysis is used to detect website vulnerabilities, then the analysis process is simple and fast, but malicious third-party scripts injected into trusted libraries cannot be identified

Engineering Contradiction:
Improvevulnerability detection speedVSAvoiddetection accuracy of malicious scripts
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The patent transitions from static analysis to dynamic analysis by executing website code in a controlled runtime environment. This allows the system to observe actual script behavior during execution, enabling detection of malicious third-party scripts that static analysis cannot identify. The dynamic approach monitors events as they occur during website operation rather than analyzing code in isolation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes the state of code execution from static (non-executing) to dynamic (runtime execution). By evaluating code in a controlled runtime environment with monitored events, the system transforms the detection process to observe actual behavior patterns, character frequency statistics, and execution flow that reveal malicious scripts while maintaining analysis speed through automated event processing.

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If manual website code analysis is performed to identify vulnerabilities, then detection thoroughness is high, but the process is time-consuming and inefficient

Engineering Contradiction:
Improvevulnerability detection thoroughnessVSAvoidanalysis time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system implements automated event-based analysis that performs comprehensive vulnerability detection without manual intervention. The runtime environment automatically executes code, captures events, and applies analysis rules to identify malicious scripts. This self-service approach maintains high detection thoroughness by systematically analyzing all code paths while eliminating the time cost of manual analysis through automation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical analysis processes with automated computational systems. The system uses event-driven automation to execute code, capture behavioral events, and apply detection rules algorithmically. This substitution maintains thorough detection capabilities while dramatically reducing analysis time by eliminating human manual inspection in favor of automated runtime monitoring and event processing.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Device complexity

If traditional security testing methods are used, then the testing framework is simple, but real-time detection of security threats is not achieved

Engineering Contradiction:
Improvetesting framework simplicityVSAvoidreal-time security detection capability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The system implements real-time security detection by dynamically executing website code in a controlled runtime environment and monitoring events as they occur during actual operation. This dynamic approach enables immediate identification of malicious scripts and security threats while they are being executed, providing real-time detection capability that traditional static testing frameworks cannot achieve.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system establishes a feedback loop where runtime events are continuously captured, analyzed against security rules, and used to immediately identify security threats. The event-based architecture provides real-time feedback on code behavior, allowing the system to detect and alert on malicious activities as they occur during website execution rather than requiring separate testing phases.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12506764B2Event and rule-based dynamic security test system
Publication Date: 2025.12.23 TARGET BRANDS INC
  • US12506764B2 patent drawing
  • US12506764B2 patent drawing
  • US12506764B2 patent drawing

AI summary

The disclosed technology provides for performing website anomaly tests by automatically checking whether a website is compromised by malicious code. A system can test dynamic behavior of the website indicating a functional user flow through the website. A set of rules can be applied against a log of the behavior and static code of the website to identify potential compromises. A first rule can be satisfied based on identifying patterns of plain text encodings in portions of website event data. A second rule can be applied to the portions of event data representing information transmitted from a client device to a third party device. The second rule can be satisfied based on identifying third party account information that is not included in a whitelist of allowed third party accounts information. A likelihood of potential security vulnerability can also be determined based on the first and/or second rules being satisfied.