GCVE-1988-2026-0242

Vulnerability from gna-1988 – Published: 2026-09-08 08:13 – Updated: 2026-09-08 08:13
VLAI
Title
UPDATE: Ant Group Censors 4 Security Research Articles After Initial Complaint Rejection
Summary
[This is an update to communications sent March 12-14 regarding Alipay security vulnerabilities.] --- On March 15, 2026, four WeChat articles documenting security vulnerabilities in Alipay were forcibly deleted from the public account AI-security-innora. The deletion was carried out by Tencent at the request of Beijing Geyun Law Firm, acting on behalf of Ant Group, citing China's Cybersecurity Law. The same complaint had been rejected by WeChat four days earlier on grounds of "reputation infringement" -- at that point WeChat found it did not meet the threshold for removal. When resubmitted under a different legal theory, the articles were deleted without further review. --- WHAT WAS DELETED 1. "Whitelist bypass as a universal attack key" (当白名单绕过沦为全网攻击的钥匙) 2. "The gag order rejected by WeChat, then reversed" (巨头的封口令被微信驳回) 3. "GPS location silently exfiltrated from 1B+ users' payment app" (位置被秒偷) 4. "Security research vs. a cease-and-desist for an article with zero mentions of Alipay" --- THE BROADER DISCLOSURE RECORD The underlying research covers 17 vulnerabilities (CVSS 7.4-9.3) in Alipay for iOS/Android, reported to Ant Group through responsible disclosure. Ant Group's formal response: "normal functionality." Independent verification and institutional acceptance: - MITRE: 6 CVEs accepted, Ticket #2005801 - Packet Storm: Advisory #217089 published - CSSF Luxembourg: Whistleblowing case CSSFWB-2026-080 - HKMA Hong Kong: Case CE20260313175412 - PDPC Singapore: Investigation #00629724 - Apple Product Security: Case OE01052449093014 - Google Play: Policy violation review #9-7515000040640 - CIRCL Luxembourg: Case #4782984 (relayed to Alibaba SRC) - 38+ institutions across 22 jurisdictions have acknowledged the report Full technical report: https://innora.ai/zfb/ GitHub: https://github.com/sgInnora/alipay-deeplink-research --- THE CENSORSHIP PATTERN This escalation follows a documented sequence: 1. Oral denial by vendor ("normal functionality," March 10) 2. Public blog published after disclosure window elapsed (March 11) 3. Cease-and-desist via Beijing Geyun Law Firm (March 11, 4h29m after publication) 4. Initial WeChat complaint REJECTED (reputation infringement standard not met) 5. Re-filed under Cybersecurity Law -- all 4 articles deleted without further notice (March 15) 6. Server-side blocking of PoC demonstration traffic (documented separately) This pattern is consistent with suppression of security research rather than legitimate legal remedy. disclose.io maintains a researcher threats database at https://threats.disclose.io/ that tracks this category of legal and platform-based retaliation against good-faith researchers. A full bilingual analysis of this censorship event is available at: https://innora.ai/zfb/ --- I am available for verification, additional documentation, or technical questions. Jiqiang Feng Innora AI Security Research feng () innora ai https://innora.ai/zfb/ _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
VULNARCHIVE GNA GNA-1988
GNA scorecard E 38/100 over 581 records in the last 180 days details
Impacted products
Vendor Product Version CPE status
unknown UPDATE Ant Group Affected: unknown
guessed Create a notification for this product.

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "UPDATE Ant Group",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Jiqiang Feng via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "[This is an update to communications sent March 12-14 regarding Alipay security vulnerabilities.]\n\n---\n\nOn March 15, 2026, four WeChat articles documenting security vulnerabilities in Alipay were forcibly deleted from the \npublic account AI-security-innora. The deletion was carried out by Tencent at the request of Beijing Geyun Law Firm, \nacting on behalf of Ant Group, citing China\u0027s Cybersecurity Law.\n\nThe same complaint had been rejected by WeChat four days earlier on grounds of \"reputation infringement\" -- at that \npoint WeChat found it did not meet the threshold for removal. When resubmitted under a different legal theory, the \narticles were deleted without further review.\n\n---\n\nWHAT WAS DELETED\n\n1. \"Whitelist bypass as a universal attack key\" (\u5f53\u767d\u540d\u5355\u7ed5\u8fc7\u6ca6\u4e3a\u5168\u7f51\u653b\u51fb\u7684\u94a5\u5319)\n2. \"The gag order rejected by WeChat, then reversed\" (\u5de8\u5934\u7684\u5c01\u53e3\u4ee4\u88ab\u5fae\u4fe1\u9a73\u56de)\n3. \"GPS location silently exfiltrated from 1B+ users\u0027 payment app\" (\u4f4d\u7f6e\u88ab\u79d2\u5077)\n4. \"Security research vs. a cease-and-desist for an article with zero mentions of Alipay\"\n\n---\n\nTHE BROADER DISCLOSURE RECORD\n\nThe underlying research covers 17 vulnerabilities (CVSS 7.4-9.3) in Alipay for iOS/Android, reported to Ant Group \nthrough responsible disclosure. Ant Group\u0027s formal response: \"normal functionality.\"\n\nIndependent verification and institutional acceptance:\n- MITRE: 6 CVEs accepted, Ticket #2005801\n- Packet Storm: Advisory #217089 published\n- CSSF Luxembourg: Whistleblowing case CSSFWB-2026-080\n- HKMA Hong Kong: Case CE20260313175412\n- PDPC Singapore: Investigation #00629724\n- Apple Product Security: Case OE01052449093014\n- Google Play: Policy violation review #9-7515000040640\n- CIRCL Luxembourg: Case #4782984 (relayed to Alibaba SRC)\n- 38+ institutions across 22 jurisdictions have acknowledged the report\n\nFull technical report: https://innora.ai/zfb/\nGitHub: https://github.com/sgInnora/alipay-deeplink-research\n\n---\n\nTHE CENSORSHIP PATTERN\n\nThis escalation follows a documented sequence:\n\n1. Oral denial by vendor (\"normal functionality,\" March 10)\n2. Public blog published after disclosure window elapsed (March 11)\n3. Cease-and-desist via Beijing Geyun Law Firm (March 11, 4h29m after publication)\n4. Initial WeChat complaint REJECTED (reputation infringement standard not met)\n5. Re-filed under Cybersecurity Law -- all 4 articles deleted without further notice (March 15)\n6. Server-side blocking of PoC demonstration traffic (documented separately)\n\nThis pattern is consistent with suppression of security research rather than legitimate legal remedy. disclose.io \nmaintains a researcher threats database at https://threats.disclose.io/ that tracks this category of legal and \nplatform-based retaliation against good-faith researchers.\n\nA full bilingual analysis of this censorship event is available at: https://innora.ai/zfb/\n\n---\n\nI am available for verification, additional documentation, or technical questions.\n\nJiqiang Feng\nInnora AI Security Research\nfeng () innora ai\nhttps://innora.ai/zfb/\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-08T08:13:41Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Mar/7"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Mar/7"
        },
        {
          "url": "https://github.com/sgInnora/alipay-deeplink-research"
        },
        {
          "url": "https://innora.ai/zfb/"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://threats.disclose.io/"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Mar/7"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "UPDATE: Ant Group Censors 4 Security Research Articles After Initial Complaint Rejection",
      "x_gcve": [
        {
          "recordType": "advisory",
          "relationships": [],
          "vulnId": "GCVE-1988-2026-0242",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Mar/7",
            "automated": true,
            "contentSha256": "f12bb476b564c255d13e198a5fb0e7a28d725ccca29027603773149a484a6d65",
            "evidenceScore": 7,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Mar/7",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-03-15T12:18:43Z"
          }
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-08T08:13:41Z",
    "dateUpdated": "2026-09-08T08:13:41Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0242"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.