technology software

documentation technical

cryptocurrency blockchain

English

The domain name '185.135.80.216:8080' uses an unknown top-level domain with no subdomain. The registrable portion '185.135.80.216' spans 14 characters holding zero vowels versus zero consonants, notching 11 digits. Word splitting yields four words: 185, 135, 80, 216. Median word length is three characters. No strong language cues emerged from the frequency lists.

589246a2b38bfb58013f7e1b256149c69b3323dd5835b365a7ec882b0517d7ab

f33a2d78362bde001670e3a29b01fd0dc16a7f9194d042a775af89270ab38b74

1499a72ba22ab7037f8f23dc9f0a84d8c2c0f8e83b641bef56d90d4831a9a696

7d876707e753974b80e455561e82dff0e7f7a0fa408c584003ead9ea337f75bf

b768d3bfbc80fcf42cdec946777feafe587133fd496ca75db9a0b2dc64f320c2

11e82953f9a1018a12e8843795c7e69112ec18628a15357de12aac7342230a5b

9c17cab6ab49fda358227f1e1015fa8f2417614e37ce3d4756edf8269ad3c97c

e9f2925331e26ca5b93a2289d00640113768fe8d394ae8e315f7b2ce5c288815

7b2bf3bba99febde8df84694b003053d3809cc04ace5d1f9a3e74b2c0cf56795

dafc2088fb1e331cba988f488815373e0c29ebf2b202b11cda5527daf66debf1

e04d1738f8920c8c95b43bf6d5e95b04343325789df5c42bc4fc0cd5b66bd024

c9506197caf809a075b6dee1da0d36fb19da7158ffe8a88e7b0c96c5d8623c99

090d977d3bf7e695615aa246dbd27c9b9f4e9875fbcebc7cf4432fd0d5b0f454

81b7ad513e3ebcf0b8c6bb88e9a6d0ea04e26f42f4e46a8c97a6735ecdbabbf3

df66b929dbb1bef6f8ab9303a388a9818aa1e521e5963486b0e8988cbcd99b63

4265f0268480ac9444c24a28837751ed926640ac0440c0300edbda91d2b9f18d

171d06c6f769cbda3b02f5e8fbb1e83761cfdd38ea3c35e6bfdf30c51639bd1c

07efa71fc52faebf372d1632d15292379c7e72cdb7e06d4f36327f97ba2f71e6

fcad1b949bc99bc4e9434805bfcda6c1b8ab2f1a170a8160bc9bd694abf74ce6

3a98d852b6bee7154f063223d0ee6f578472dad5a58f5dbd03dcf31d8d0800b8

f120d81c79b8069bbc362f9bf186f8724980a1c21afb3460f781e94e6db06bd1

92fcd56650e0ba6475e79aeb40a4a37d9385c4e7b396557f0d8ccdf7b9396ad4

630877bb6e77257d6c06e156c3f402a1c4f2eb53ea96e6e3169787fdd7e9b0b8

bf90cd21c3a6232ffd6688d08290a42829535a718d35a8a1cc46fd01adb8230b

c199e3a4b2ba191d65d5b4f71e4a997522a88d9fd2e5879edbefa87524ab6434

0c1201ffc90c4ea6046754efe27c6d3d17ab74df6680d7395dfa4e5eb3c661dc

76c7e23551eb059adc50db88863b47421624bef748843135fd0a37e0a3451c5f

08b68ec35a5e10d869893615b2d89f630937336cc29a60ace87a1436791a76a7

7e77fbd6c04005141b70a106561268173057e39e159efe0977fbe9f6de40783e

49ab70ea4d51eeb59b9f2dd723f9d9c016cfe93f56af8ffffb76220e4719fa63

d6e505b2efe95e9884d64ca103cabcd7c8c1cd48976f7dd202af4c4c90e9aba9

f558fbf1253dd2ec6f39bb1f9c661ba1470370eadecd5893fda7a32768704466

f8a966da313418fd70fbab47ae2c4fb0fc91ca017cf576c65dfe3ac2c2cf172d

069b58bb65d96b5a652ce834cccd1d5839c9cc564768bf16c2ab6f9736481480

2761bb4859d83496e48e0932b93d577d3b0f651c40da445966c08e91658d24ef

b815a43f2ba765bb0116c2bfaaa60c98732b491812a2e38d42e7ae56b3ba4297

113b96d4988b9283c5392ba88daa51f092602bf5e746d23de18587a8f43a2b3c

b3a9862f74955dfd20ccd8359fd2012c7981498d3594d381a08ab79ddb55c002

58385ca616a0c8fe72ff382966512e1fd6993ed64a707c778ae61d491a4582ae

d71eea919ec9c8851798bcec81a5bd1b45a07a9356d0919482477da17b41caa6

d5fb6d8f811a44a1df13b2398113160e478b50a8871026ccca4aced02dc3ec6d

323bac53f364f9248f08c10c8daaeac91e848b5d413135b5b6c78d8dd255ef4c

ec0945245c894a4bd6e7cec90880c44c0478471271676a9be08777cc742aee24

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

d5773718215a5102823dcf0be71426eea2c95d96ed323f6c8de9f015e95c3bdc

viewport

HSTS header missing - vulnerable to protocol downgrade attacks

CSP header missing - vulnerable to XSS attacks

XS Cyberstrikeal (Barnes | (Gem | [ Gsm | | Gengin | | + | | = |
|< || Dashboard @ Lastupdated - | Refresh |
WORKSPACE
SECURITY OPERATIONS
Running conversations Total vuinerabilties oO Too! invacations A Tool success rate v
CAPABILITIES
ADMINISTRATION an an ane ane
oe
Vulnerability severity distribution Sign in to CyberStrikeAl © Allstatuses v | Viewal- ‘Batch task queues View al =
Sign in with a platform account. The default
( \ administrator is admin. i
Risk level Safe a NN
© Critical o 0%
Weighted risk score ° _ Pending Running Completed
ÅL ) ao Username © High o 0% A PAN VEN J
Open ;
_——— ,-—__. admin © Medium DD. 0%
(I (I
Critical High Password © Low o 0% :
Å ÅR J Tool execution count View al =
Latest found . | Enter password © Info o 0%
None yet sg
( Vf "| - @19) Loading... i
0 0 (I i 9 |
| Open Confirmed Fixed False postive | |
L IR ) \ J eFixed a Confirmed 0 Open |
! i

4 MCP tools

|| B skills

| FRE Korg |



Abuse-C Role

Vladimir E Gnat

MNT-ADMAN

Adman LLC

ORG-NCC1-RIPE

ORG-NGs2-RIPE

RU-ADMAN-20160120


        
        if (typeof ELK === 'undefined' && typeof elk !== 'undefined') {
            window.ELK = elk;
        }
    

Marked

CyberStrikeAI

regular

⚠️ High Risk - http://185.135.80.216:8080/

Requests	IP Address	Location	AS Autonomous System
51	185.135.80.216	Russia	AS57494Adman LLC
51	1	-	-

Security Scan Report: 185.135.80.216

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