Skip to Main Content
Status Submitted
Workspace * IBM Cloud Ideas
Categories Compliance
Created by Guest
Created on Nov 19, 2026

Abnormal Application Behavior Monitoring Record

PROBLEM: When software is modified to secretly monitor, manipulate, or harm its users, the first sign is usually abnormal behavior — unexpected network traffic, unexplained permission use, or functions running that the user never asked for. The documented pattern is old: LoJax (ESET, September 2018) hid in firmware so it survived a Windows reinstall and a hard-drive replacement, and Abaddon RAT (first seen October 22, 2020) took orders from a Discord channel so its control traffic hid in a legitimate platform. No single record ties an application's observed behavior to its expected behavior, so tampered software is usually found only after the harm is done.

SOLUTION: An abnormal application behavior monitoring record: every application logged with its expected behavior profile and every deviation — new network destinations, new permissions, new background activity — scored against that profile, so a modified application is flagged on its own behavior before its users are harmed.

EVIDENCE BASIS: DOCUMENTED — LoJax: ESET white paper, Sept 2018 (first UEFI rootkit found in the wild; at least one confirmed SPI flash install; survives OS reinstall and hard-drive replacement). Abaddon RAT: first seen Oct 22, 2020 (MalwareHunterTeam); Discord control channel; steals browser/game logins; remote shell (see AX-07). Sources: welivesecurity.com (ESET LoJax PDF); BleepingComputer.

Idea priority Low
Needed By Not sure -- Just thought it was cool