technology software

documentation technical

government public service

cryptocurrency blockchain

Chinese

Domain '101.96.237.195:8081' uses an unknown top-level domain. Count 14 characters in '101.96.237.195' holding zero vowels versus 0 consonants, plus eleven digits. Splitting it apart reveals 4 words: 101, 96, 237, 195. Median word length comes out to 3 characters. No strong language cues emerged from the frequency lists.

f33a2d78362bde001670e3a29b01fd0dc16a7f9194d042a775af89270ab38b74

b3bf6a1520dab8ab30be7219caca75a854c2d45aa83f76b7f2b6fc4c83a0d916

1499a72ba22ab7037f8f23dc9f0a84d8c2c0f8e83b641bef56d90d4831a9a696

11e82953f9a1018a12e8843795c7e69112ec18628a15357de12aac7342230a5b

dafc2088fb1e331cba988f488815373e0c29ebf2b202b11cda5527daf66debf1

b768d3bfbc80fcf42cdec946777feafe587133fd496ca75db9a0b2dc64f320c2

7d876707e753974b80e455561e82dff0e7f7a0fa408c584003ead9ea337f75bf

f2fb143cce8802eb28c503ccaae50f51399cec0b20800aecfdbdd311f26f5ffe

e9f2925331e26ca5b93a2289d00640113768fe8d394ae8e315f7b2ce5c288815

9c17cab6ab49fda358227f1e1015fa8f2417614e37ce3d4756edf8269ad3c97c

e04d1738f8920c8c95b43bf6d5e95b04343325789df5c42bc4fc0cd5b66bd024

c8fcbe8089c22b973e4f82305f755e8df492d30ea64a80c9c73ab4db1d07f350

090d977d3bf7e695615aa246dbd27c9b9f4e9875fbcebc7cf4432fd0d5b0f454

40e319d616ab37c3912806e08eeb0f52f932776f7f01f13b04c9205f4fb13a38

c9506197caf809a075b6dee1da0d36fb19da7158ffe8a88e7b0c96c5d8623c99

df66b929dbb1bef6f8ab9303a388a9818aa1e521e5963486b0e8988cbcd99b63

3a98d852b6bee7154f063223d0ee6f578472dad5a58f5dbd03dcf31d8d0800b8

92fcd56650e0ba6475e79aeb40a4a37d9385c4e7b396557f0d8ccdf7b9396ad4

2edba5f95d5416fe670fabca0600263920d52d70f2203353d75ed189139f05ec

ea0eab54c3e66a722490ac2143a7569e01e8f5816ba0a7495240535c2c9e8388

DOMPurify allows tampering by prototype pollution

DOMPurify allows Cross-site Scripting (XSS)

When USE_PROFILES is enabled, DOMPurify rebuilds ALLOWED_ATTR as a plain array whose properties are looked up by name, making it susceptible to prototype pollution. If Array.prototype has been polluted with an event handler attribute name (e.g. onclick), DOMPurify will allow that event handler to survive sanitization, resulting in DOM-based XSS.

DOMPurify's ADD_ATTR predicate function mechanism (via EXTRA_ELEMENT_HANDLING.attributeCheck) short-circuits URI validation when the predicate returns true. This allows unsafe protocols such as javascript: to survive sanitization in href and similar attributes, enabling DOM-based XSS when such links are activated.

DOMPurify is vulnerable to mutation-XSS (mXSS) when sanitized HTML is embedded into special raw-text wrapper elements such as xmp, script, iframe, noembed, noframes, or noscript before being assigned via innerHTML. Attacker-controlled sequences like </xmp> inside attribute values close the raw-text context during the second parse, causing the sanitized output to mutate into executable markup.

DOMPurify has a logic inconsistency where FORBID_TAGS is not checked when a function-based ADD_TAGS (tagCheck) returns true. Due to short-circuit evaluation, the FORBID_TAGS check is never evaluated, allowing explicitly forbidden elements to pass through sanitization when EXTRA_ELEMENT_HANDLING.tagCheck is configured.

DOMPurify has an asymmetric security inconsistency where FORBID_TAGS does not win over a function-based ADD_TAGS predicate, while FORBID_ATTR correctly wins over ADD_ATTR. When ADD_TAGS is provided as a function that returns true, explicitly forbidden tags such as iframe and form pass through sanitization with their attributes intact.

DOMPurify's SAFE_FOR_TEMPLATES feature fails to strip Mustache/template expressions when RETURN_DOM or RETURN_DOM_FRAGMENT is used. The final string-scrubbing pass that removes expressions like {{...}} is skipped in DOM-return mode, and split text nodes (e.g. from removed intermediate tags) can rejoin to form a complete expression that template-evaluating frameworks like Vue 2 will execute.

DOMPurify versions 3.0.1 through 3.3.3 are vulnerable to an XSS bypass via prototype pollution. When no CUSTOM_ELEMENT_HANDLING is specified, the fallback plain object inherits from Object.prototype; if an attacker has polluted Object.prototype.tagNameCheck and Object.prototype.attributeNameCheck with permissive regexes, DOMPurify allows arbitrary custom elements with event handler attributes through sanitization.

DOMPurify: Cross-realm IN_PLACE sanitization leaves executable markup intact via realm-bound `instanceof` checks

DOMPurify: IN_PLACE mode preserves attributes of a clobbered root element, allowing XSS via attacker-controlled root DOM

DOMPurify: Hook mutation of `data.allowedTags` / `data.allowedAttributes` permanently pollutes `DEFAULT_ALLOWED_TAGS` / `DEFAULT_ALLOWED_ATTR`

DOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside <template>.content

DOMPurify: `IN_PLACE` mode trusts attacker-controlled `nodeName` on live non-form nodes, allowing script retention and XSS via attacker-supplied DOM objects

DOMPurify: SAFE_FOR_TEMPLATES bypass - template expressions survive sanitization inside <template> content when using DOM output modes

DOMPurify: Trusted Types policy survives `clearConfig()` and can poison later `RETURN_TRUSTED_TYPE` output

DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch)

DOMPurify: `CUSTOM_ELEMENT_HANDLING` bypasses `afterSanitizeElements` for allowed custom elements.

DOMPurify: IN_PLACE hook removal leaves a detached subtree executable, causing XSS

DOMPurify: IN_PLACE returns a force-removed rawtext root whose text carries attacker markup — pure HTML reparse executes

DOMPurify: SMIL attributeName=href guard is skipped when PARSER_MEDIA_TYPE is application/xhtml+xml

DOMPurify IN_PLACE: hook that removes a parent or sibling leaves the detached subtree's event handlers armed (incomplete fix for GHSA-p98j-92pf-mc4p)

4ed913f5ffd0817b8c0df7e6e4c535efb1e6c1eb7b8069f53af12b9e90109eef

33fcafc31a013417c087daa44b6a56303b7c62ef9b420f609845e3a323d67521

4265f0268480ac9444c24a28837751ed926640ac0440c0300edbda91d2b9f18d

viewport

HSTS header missing - vulnerable to protocol downgrade attacks

CSP header missing - vulnerable to XSS attacks

IRT-VOLCANO-ENGINE-CN

Chen Qi

Liu Nian

VOLCANO-ENGINE


        (function () {
            var initialPage = String(window.location.hash || '').replace(/^#/, '').split('?')[0];
            if (initialPage && initialPage !== 'dashboard') {
                document.documentElement.classList.add('initial-route-pending');
            }
        })();
    

Marked

DarkAI

regular

⚠️ High Risk - http://101.96.237.195:8081/

Requests	IP Address	Location	AS Autonomous System
53	101.96.237.195	China	AS137718Beijing Volcano Engine Technology Co., Ltd.
53	1	-	-

Security Scan Report: 101.96.237.195

Summary

AI Security Verdict

High Risk

Details

Screenshot

Page Load Overview

Language Analysis

Primary Language

Detection Details

Website Classification

Primary Category

All Detected Categories

Detected Features

Domain & IP Information

Detected Technologies1

Content Similarity HashesFor malware variant detection

TLSH (Trend Micro Locality Sensitive Hash)

ssdeep (Context Triggered Piecewise Hashing)

sdhash (Similarity Digest Hashing)

Image Hashes

Perceptual Hashes

Other Hashes

Scan History