MétaCan
Menu
Back to cohort
Record W7104178648 · doi:10.5267/j.ijdns.2025.9.004

Client-side runtime integrity agent for detecting man-in-the-browser attacks using forensic monitoring and anomaly detection

2025· article· en· W7104178648 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueInternational Journal of Data and Network Science · 2025
Typearticle
Languageen
FieldComputer Science
TopicWeb Application Security Vulnerabilities
Canadian institutionsnot available
FundersKing Faisal University
KeywordsAnomaly detectionOverhead (engineering)EncryptionIntrusion detection systemData integrityClass (philosophy)

Abstract

fetched live from OpenAlex

Man-in-the-Browser (MitB) attacks represent a sophisticated class of web-based threats that manipulate browser functionality to intercept and modify user transactions in real-time. Traditional server-side detection mechanisms often fail to identify these attacks due to their client-side nature and encrypted communication channels. This paper presents a novel client-side runtime integrity agent that employs forensic monitoring and machine learning-based anomaly detection to identify MitB attacks at their source. The proposed system integrates DOM integrity verification, memory forensic analysis, and behavioral pattern recognition to detect malicious browser modifications before they can compromise user sessions. Our experimental evaluation demonstrates a detection accuracy of 97.3% with a false positive rate of 2.1%, significantly outperforming existing client-side detection methods. The system successfully identified various MitB attack vectors, including Zeus, SpyEye, and custom injection payloads, while maintaining a minimal computational overhead of less than 3% CPU utilization.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.837
Threshold uncertainty score0.543

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0010.002
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.061
GPT teacher head0.367
Teacher spread0.305 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it