Comparison Overview
XOOCITY Hong Kong Metaverse 数宇城香港

XOOCITY Hong Kong Metaverse 数宇城香港
Hong Kong Science and Technology Park., Hong Kong, HK
Last Update: 15/12/2025
XOOCITY is pioneering a virtual metaverse named CitiFi, designed to seamlessly integrate trade, tourism, job opportunities, and social interactions. By harnessing the power of blockchain technology and real-world assets, we have created a platform for trading virtual as...

Flipkart
Flipkart Internet Private Limited, Buildings Alyssa, Begonia & Clove Embassy Tech Village, Outer Ring Road, Devarabeesanahalli Village, Bangalore, Karnataka, IN, 560103
Last Update: 08/09/2026
At Flipkart, we're driven by our purpose of empowering every Indian's dream by delivering value through innovation in technology and commerce. With a customer base of over 350 million, product coverage of over 150 million across 80+ categories, a focus on generating dir...
Compliance Ranges Comparison

XOOCITY Hong Kong Metaverse 数宇城香港







Flipkart






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for XOOCITY Hong Kong Metaverse 数宇城香港 in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Flipkart has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - XOOCITY Hong Kong Metaverse 数宇城香港 (X = Date, Y = Severity)
XOOCITY Hong Kong Metaverse 数宇城香港 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Flipkart (X = Date, Y = Severity)
Flipkart cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

XOOCITY Hong Kong Metaverse 数宇城香港

Flipkart
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.