feat(security): implement rapid asset draining detection utility and metrics compiler#205
Merged
mijinummi merged 1 commit intoJul 19, 2026
Conversation
9 tasks
Collaborator
|
LGTM! Well done for this beautiful work.. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎯 Core Overview
Problem Statement
The security platform processes ledger transfers individually, but lacks a mechanism to evaluate the cumulative velocity of capital outflows. Without rolling window telemetry, multi-transaction smart contract compromises or rapid treasury draining attacks go unnoticed until balances are depleted.
Proposed Solution
This PR implements the codebase layout for issue #143. It introduces an
AssetDrainDetectorthat processes outbound transfers over a 5-minute rolling window. If outflows cross safe values ($50k USD or 20% of total treasury value), the engine automatically registers a high/critical degradation factor to lower the organization's security posture score instantly.Closes #143
🛠️ Technical Implementation Details
1. Rolling Outflow Calculations
2. Multi-Tier Severity Scaling
MEDIUM, crossing baseline limits toHIGH, and major losses (>50% capitalization) toCRITICAL, generating up to a 40-point posture reduction.📋 Quality Assurance Matrix
npm run build).