home.social

#data_exfiltration โ€” Public Fediverse posts

Live and recent posts from across the Fediverse tagged #data_exfiltration, aggregated by home.social.

  1. ๐”๐ง๐ข๐ฏ๐ž๐ซ๐ฌ๐ข๐ญ๐š๐ญ ๐๐ž ๐•๐š๐ฅ๐žฬ€๐ง๐œ๐ข๐š ๐“๐š๐ซ๐ ๐ž๐ญ๐ž๐ ๐›๐ฒ ๐๐จ๐ฏ๐š ๐†๐ซ๐จ๐ฎ๐ฉ: ๐Ÿ‘๐ŸŽ๐ŸŽ๐†๐ ๐ƒ๐š๐ญ๐š ๐„๐ฑ๐Ÿ๐ข๐ฅ๐ญ๐ซ๐š๐ญ๐ข๐จ๐ง ๐‚๐ฅ๐š๐ข๐ฆ๐ž๐, ๐ˆ๐ง๐ข๐ญ๐ข๐š๐ฅ $๐Ÿ“๐ŸŽ๐ŸŽ,๐ŸŽ๐ŸŽ๐ŸŽ ๐‘๐š๐ง๐ฌ๐จ๐ฆ ๐ƒ๐ž๐ฆ๐š๐ง๐ ๐‘๐ž๐ฏ๐ž๐š๐ฅ๐ž๐

    News of the attack was initially reported by the online newspaper Escudo Digital in an article by journalist Alberto Payo, which included statements attributed to a member of the universityโ€™s IT team. These details are now complemented by statements provided exclusively to SuspectFile.com directly by the Nova group, introducing additional information that had not previously emerged publicly, including an alleged initial ransom demand of $500,000.

    suspectfile.com/universitat-de

    #Data_Breach #Data_Exfiltration #Nova #Ransomoware #Universitat_de_Valรจncia

  2. ๐”๐ง๐ข๐ฏ๐ž๐ซ๐ฌ๐ข๐ญ๐š๐ญ ๐๐ž ๐•๐š๐ฅ๐žฬ€๐ง๐œ๐ข๐š ๐“๐š๐ซ๐ ๐ž๐ญ๐ž๐ ๐›๐ฒ ๐๐จ๐ฏ๐š ๐†๐ซ๐จ๐ฎ๐ฉ: ๐Ÿ‘๐ŸŽ๐ŸŽ๐†๐ ๐ƒ๐š๐ญ๐š ๐„๐ฑ๐Ÿ๐ข๐ฅ๐ญ๐ซ๐š๐ญ๐ข๐จ๐ง ๐‚๐ฅ๐š๐ข๐ฆ๐ž๐, ๐ˆ๐ง๐ข๐ญ๐ข๐š๐ฅ $๐Ÿ“๐ŸŽ๐ŸŽ,๐ŸŽ๐ŸŽ๐ŸŽ ๐‘๐š๐ง๐ฌ๐จ๐ฆ ๐ƒ๐ž๐ฆ๐š๐ง๐ ๐‘๐ž๐ฏ๐ž๐š๐ฅ๐ž๐

    News of the attack was initially reported by the online newspaper Escudo Digital in an article by journalist Alberto Payo, which included statements attributed to a member of the universityโ€™s IT team. These details are now complemented by statements provided exclusively to SuspectFile.com directly by the Nova group, introducing additional information that had not previously emerged publicly, including an alleged initial ransom demand of $500,000.

    suspectfile.com/universitat-de

    #Data_Breach #Data_Exfiltration #Nova #Ransomoware #Universitat_de_Valรจncia

  3. ๐”๐ง๐ข๐ฏ๐ž๐ซ๐ฌ๐ข๐ญ๐š๐ญ ๐๐ž ๐•๐š๐ฅ๐žฬ€๐ง๐œ๐ข๐š ๐“๐š๐ซ๐ ๐ž๐ญ๐ž๐ ๐›๐ฒ ๐๐จ๐ฏ๐š ๐†๐ซ๐จ๐ฎ๐ฉ: ๐Ÿ‘๐ŸŽ๐ŸŽ๐†๐ ๐ƒ๐š๐ญ๐š ๐„๐ฑ๐Ÿ๐ข๐ฅ๐ญ๐ซ๐š๐ญ๐ข๐จ๐ง ๐‚๐ฅ๐š๐ข๐ฆ๐ž๐, ๐ˆ๐ง๐ข๐ญ๐ข๐š๐ฅ $๐Ÿ“๐ŸŽ๐ŸŽ,๐ŸŽ๐ŸŽ๐ŸŽ ๐‘๐š๐ง๐ฌ๐จ๐ฆ ๐ƒ๐ž๐ฆ๐š๐ง๐ ๐‘๐ž๐ฏ๐ž๐š๐ฅ๐ž๐

    News of the attack was initially reported by the online newspaper Escudo Digital in an article by journalist Alberto Payo, which included statements attributed to a member of the universityโ€™s IT team. These details are now complemented by statements provided exclusively to SuspectFile.com directly by the Nova group, introducing additional information that had not previously emerged publicly, including an alleged initial ransom demand of $500,000.

    suspectfile.com/universitat-de

    #Data_Breach #Data_Exfiltration #Nova #Ransomoware #Universitat_de_Valรจncia

  4. ๐”๐ง๐ข๐ฏ๐ž๐ซ๐ฌ๐ข๐ญ๐š๐ญ ๐๐ž ๐•๐š๐ฅ๐žฬ€๐ง๐œ๐ข๐š ๐“๐š๐ซ๐ ๐ž๐ญ๐ž๐ ๐›๐ฒ ๐๐จ๐ฏ๐š ๐†๐ซ๐จ๐ฎ๐ฉ: ๐Ÿ‘๐ŸŽ๐ŸŽ๐†๐ ๐ƒ๐š๐ญ๐š ๐„๐ฑ๐Ÿ๐ข๐ฅ๐ญ๐ซ๐š๐ญ๐ข๐จ๐ง ๐‚๐ฅ๐š๐ข๐ฆ๐ž๐, ๐ˆ๐ง๐ข๐ญ๐ข๐š๐ฅ $๐Ÿ“๐ŸŽ๐ŸŽ,๐ŸŽ๐ŸŽ๐ŸŽ ๐‘๐š๐ง๐ฌ๐จ๐ฆ ๐ƒ๐ž๐ฆ๐š๐ง๐ ๐‘๐ž๐ฏ๐ž๐š๐ฅ๐ž๐

    News of the attack was initially reported by the online newspaper Escudo Digital in an article by journalist Alberto Payo, which included statements attributed to a member of the universityโ€™s IT team. These details are now complemented by statements provided exclusively to SuspectFile.com directly by the Nova group, introducing additional information that had not previously emerged publicly, including an alleged initial ransom demand of $500,000.

    suspectfile.com/universitat-de

    #Data_Breach #Data_Exfiltration #Nova #Ransomoware #Universitat_de_Valรจncia

  5. ๐”๐ง๐ข๐ฏ๐ž๐ซ๐ฌ๐ข๐ญ๐š๐ญ ๐๐ž ๐•๐š๐ฅ๐žฬ€๐ง๐œ๐ข๐š ๐“๐š๐ซ๐ ๐ž๐ญ๐ž๐ ๐›๐ฒ ๐๐จ๐ฏ๐š ๐†๐ซ๐จ๐ฎ๐ฉ: ๐Ÿ‘๐ŸŽ๐ŸŽ๐†๐ ๐ƒ๐š๐ญ๐š ๐„๐ฑ๐Ÿ๐ข๐ฅ๐ญ๐ซ๐š๐ญ๐ข๐จ๐ง ๐‚๐ฅ๐š๐ข๐ฆ๐ž๐, ๐ˆ๐ง๐ข๐ญ๐ข๐š๐ฅ $๐Ÿ“๐ŸŽ๐ŸŽ,๐ŸŽ๐ŸŽ๐ŸŽ ๐‘๐š๐ง๐ฌ๐จ๐ฆ ๐ƒ๐ž๐ฆ๐š๐ง๐ ๐‘๐ž๐ฏ๐ž๐š๐ฅ๐ž๐

    News of the attack was initially reported by the online newspaper Escudo Digital in an article by journalist Alberto Payo, which included statements attributed to a member of the universityโ€™s IT team. These details are now complemented by statements provided exclusively to SuspectFile.com directly by the Nova group, introducing additional information that had not previously emerged publicly, including an alleged initial ransom demand of $500,000.

    suspectfile.com/universitat-de

    #Data_Breach #Data_Exfiltration #Nova #Ransomoware #Universitat_de_Valรจncia

  6. ๐ŸŽฏ AI
    ===================

    Executive summary: Urban VPN Proxy, a Chrome extension with over 6 million users, was observed harvesting AI chat data across multiple platforms. The extension injects platform-specific executor scripts, overrides core browser network APIs, and forwards captured conversations to Urban VPN infrastructure.

    Technical details:
    โ€ข The extension deploys dedicated executor scripts (examples: chatgpt.js, claude.js, gemini.js) when targeted AI platform pages load.
    โ€ข Injected code wraps and overrides fetch and XMLHttpRequest so all request and response payloads for the page flow through the extension first.
    โ€ข Extracted fields include user prompts, model responses, conversation IDs, timestamps, session metadata, and the specific AI platform/model used.
    โ€ข Inter-script messaging uses window.postMessage with an identifier PANELOS_MESSAGE to pass parsed data to the extension content script.
    โ€ข The content script forwards packaged, compressed data to the background service worker, which transmits to endpoints such as analytics.urban-vpn.com and stats.urban-vpn.com.

    Analysis:
    โ€ข The approach is highly invasive: overriding fetch/XMLHttpRequest captures both outgoing prompts and incoming model outputs before rendering, exposing full conversation context.
    โ€ข Harvesting is independent of VPN functionality and enabled by hardcoded flags with no user-visible opt-out, increasing exposure risk for users who installed the extension for privacy reasons.

    Detection guidance:
    โ€ข Monitor outbound connections to analytics.urban-vpn.com and stats.urban-vpn.com from browser processes.
    โ€ข Inspect loaded extension scripts for executor filenames and for patterns overriding fetch/XMLHttpRequest and using window.postMessage with PANELOS_MESSAGE.

    Limitations:
    โ€ข Public reporting indicates the extension targeted ten AI platforms; specific historical timeline details were not fully enumerated in the source.
    โ€ข No CVE identifiers or named threat actor attribution were provided in the disclosed findings.

    References / Tags:
    chatgpt.js, claude.js, PANELOS_MESSAGE, analytics.urban-vpn.com

    ๐Ÿ”น ai #privacy #browser_extension #data_exfiltration

    ๐Ÿ”— Source: koi.ai/blog/urban-vpn-browser-

  7. ๐ŸŽฏ AI
    ===================

    Executive summary: Urban VPN Proxy, a Chrome extension with over 6 million users, was observed harvesting AI chat data across multiple platforms. The extension injects platform-specific executor scripts, overrides core browser network APIs, and forwards captured conversations to Urban VPN infrastructure.

    Technical details:
    โ€ข The extension deploys dedicated executor scripts (examples: chatgpt.js, claude.js, gemini.js) when targeted AI platform pages load.
    โ€ข Injected code wraps and overrides fetch and XMLHttpRequest so all request and response payloads for the page flow through the extension first.
    โ€ข Extracted fields include user prompts, model responses, conversation IDs, timestamps, session metadata, and the specific AI platform/model used.
    โ€ข Inter-script messaging uses window.postMessage with an identifier PANELOS_MESSAGE to pass parsed data to the extension content script.
    โ€ข The content script forwards packaged, compressed data to the background service worker, which transmits to endpoints such as analytics.urban-vpn.com and stats.urban-vpn.com.

    Analysis:
    โ€ข The approach is highly invasive: overriding fetch/XMLHttpRequest captures both outgoing prompts and incoming model outputs before rendering, exposing full conversation context.
    โ€ข Harvesting is independent of VPN functionality and enabled by hardcoded flags with no user-visible opt-out, increasing exposure risk for users who installed the extension for privacy reasons.

    Detection guidance:
    โ€ข Monitor outbound connections to analytics.urban-vpn.com and stats.urban-vpn.com from browser processes.
    โ€ข Inspect loaded extension scripts for executor filenames and for patterns overriding fetch/XMLHttpRequest and using window.postMessage with PANELOS_MESSAGE.

    Limitations:
    โ€ข Public reporting indicates the extension targeted ten AI platforms; specific historical timeline details were not fully enumerated in the source.
    โ€ข No CVE identifiers or named threat actor attribution were provided in the disclosed findings.

    References / Tags:
    chatgpt.js, claude.js, PANELOS_MESSAGE, analytics.urban-vpn.com

    ๐Ÿ”น ai #privacy #browser_extension #data_exfiltration

    ๐Ÿ”— Source: koi.ai/blog/urban-vpn-browser-

  8. ๐ŸŽฏ AI
    ===================

    Executive summary: Urban VPN Proxy, a Chrome extension with over 6 million users, was observed harvesting AI chat data across multiple platforms. The extension injects platform-specific executor scripts, overrides core browser network APIs, and forwards captured conversations to Urban VPN infrastructure.

    Technical details:
    โ€ข The extension deploys dedicated executor scripts (examples: chatgpt.js, claude.js, gemini.js) when targeted AI platform pages load.
    โ€ข Injected code wraps and overrides fetch and XMLHttpRequest so all request and response payloads for the page flow through the extension first.
    โ€ข Extracted fields include user prompts, model responses, conversation IDs, timestamps, session metadata, and the specific AI platform/model used.
    โ€ข Inter-script messaging uses window.postMessage with an identifier PANELOS_MESSAGE to pass parsed data to the extension content script.
    โ€ข The content script forwards packaged, compressed data to the background service worker, which transmits to endpoints such as analytics.urban-vpn.com and stats.urban-vpn.com.

    Analysis:
    โ€ข The approach is highly invasive: overriding fetch/XMLHttpRequest captures both outgoing prompts and incoming model outputs before rendering, exposing full conversation context.
    โ€ข Harvesting is independent of VPN functionality and enabled by hardcoded flags with no user-visible opt-out, increasing exposure risk for users who installed the extension for privacy reasons.

    Detection guidance:
    โ€ข Monitor outbound connections to analytics.urban-vpn.com and stats.urban-vpn.com from browser processes.
    โ€ข Inspect loaded extension scripts for executor filenames and for patterns overriding fetch/XMLHttpRequest and using window.postMessage with PANELOS_MESSAGE.

    Limitations:
    โ€ข Public reporting indicates the extension targeted ten AI platforms; specific historical timeline details were not fully enumerated in the source.
    โ€ข No CVE identifiers or named threat actor attribution were provided in the disclosed findings.

    References / Tags:
    chatgpt.js, claude.js, PANELOS_MESSAGE, analytics.urban-vpn.com

    ๐Ÿ”น ai #privacy #browser_extension #data_exfiltration

    ๐Ÿ”— Source: koi.ai/blog/urban-vpn-browser-

  9. ๐ŸŽฏ AI
    ===================

    Executive summary: Urban VPN Proxy, a Chrome extension with over 6 million users, was observed harvesting AI chat data across multiple platforms. The extension injects platform-specific executor scripts, overrides core browser network APIs, and forwards captured conversations to Urban VPN infrastructure.

    Technical details:
    โ€ข The extension deploys dedicated executor scripts (examples: chatgpt.js, claude.js, gemini.js) when targeted AI platform pages load.
    โ€ข Injected code wraps and overrides fetch and XMLHttpRequest so all request and response payloads for the page flow through the extension first.
    โ€ข Extracted fields include user prompts, model responses, conversation IDs, timestamps, session metadata, and the specific AI platform/model used.
    โ€ข Inter-script messaging uses window.postMessage with an identifier PANELOS_MESSAGE to pass parsed data to the extension content script.
    โ€ข The content script forwards packaged, compressed data to the background service worker, which transmits to endpoints such as analytics.urban-vpn.com and stats.urban-vpn.com.

    Analysis:
    โ€ข The approach is highly invasive: overriding fetch/XMLHttpRequest captures both outgoing prompts and incoming model outputs before rendering, exposing full conversation context.
    โ€ข Harvesting is independent of VPN functionality and enabled by hardcoded flags with no user-visible opt-out, increasing exposure risk for users who installed the extension for privacy reasons.

    Detection guidance:
    โ€ข Monitor outbound connections to analytics.urban-vpn.com and stats.urban-vpn.com from browser processes.
    โ€ข Inspect loaded extension scripts for executor filenames and for patterns overriding fetch/XMLHttpRequest and using window.postMessage with PANELOS_MESSAGE.

    Limitations:
    โ€ข Public reporting indicates the extension targeted ten AI platforms; specific historical timeline details were not fully enumerated in the source.
    โ€ข No CVE identifiers or named threat actor attribution were provided in the disclosed findings.

    References / Tags:
    chatgpt.js, claude.js, PANELOS_MESSAGE, analytics.urban-vpn.com

    ๐Ÿ”น ai #privacy #browser_extension #data_exfiltration

    ๐Ÿ”— Source: koi.ai/blog/urban-vpn-browser-

  10. ๐ŸŽฏ AI

    Executive summary: New research from LayerX demonstrates a novel prompt-injection vector in Perplexityโ€™s Comet browser where a single crafted URL (no malicious page content required) can coerce the assistant to access stored user data (memory and connectors such as Gmail and Google Calendar), encode it, and exfiltrate it to an attacker-controlled endpoint.

    Technical details: The vector leverages Cometโ€™s URL query parsing to supply an attacker prompt and parameters. A specially chosen collection value caused the assistant to consult memory instead of performing a web search. The prompt can instruct the assistant to summarize items it helped create, convert the summary to base64, and POST the result to an external URL. This bypasses prior page-text prompt-injection mitigations by elevating the input channel from page text to URL parameters and by using trivial encoding to evade content-exfiltration heuristics.

    Impact analysis: Any data accessible via granted connectors (email bodies, calendar entries, contact metadata) can be harvested without credential theft or explicit user action beyond opening a link. This transforms a trusted AI browser feature into a high-risk attack surface for targetted information theft.

    Detection guidance: Log and alert on outbound POST requests to uncommon domains originating from the browser process. Inspect URL query usage patterns for unusual collection parameters and monitor assistant invocation events that reference memory retrieval. Scan request bodies for high-entropy base64 payloads tied to user contexts.

    Mitigations: Disable auto-execution of instructions derived from URL parameters; restrict or compartmentalize connector scopes (least privilege); add explicit user confirmation before memory reads or external network transmission; harden exfiltration detection by decoding and analyzing encoded payloads.

    References: Research by LayerX; demonstration involves Gmail/Calendar connectors and base64+POST exfiltration.

    ๐Ÿ”น Perplexity #Comet #promptinjection #data_exfiltration #AIBrowser

    ๐Ÿ”— Source: layerxsecurity.com/blog/cometj

  11. ๐ŸŽฏ Threat Intelligence
    ======================

    Executive summary

    This research describes how malicious Model Context Protocol (MCP)
    servers can be abused in supply-chain attacks to perform
    protocol-level tampering and data exfiltration. The article outlines a
    PoC for a malicious MCP server, server installation and host analysis,
    and discusses detection and mitigation approaches.

    Technical details
    โ€ข Target: MCP implementations and model-serving supply chains.
    โ€ข Mechanism: interception or replacement of legitimate MCP endpoints
    with malicious servers that respond with manipulated model context or
    exfiltrate sensitive payloads.
    โ€ข Reported artifacts: PoC server installation steps and a malicious
    engine running on host (no CVE identifiers were disclosed in the
    sources).

    Analysis

    Malicious MCP servers expand the attack surface at the protocol layer:
    attackers who can influence or replace MCP endpoints may inject
    crafted context, modify model prompts, or intercept model
    inputs/outputs to extract data. The risk is amplified in supply-chain
    scenarios where third-party model endpoints are accepted without
    strict validation.

    ๐Ÿ”น Attack Chain Analysis
    โ€ข Initial Access: Compromise or compromise-supply component that
    controls MCP endpoint registration or distribution (e.g., compromised
    package, CI/CD artifact, or DNS).
    โ€ข Download/Delivery: Deployment of a malicious MCP server or
    reconfiguration of routing to point clients to attacker-controlled
    MCP.
    โ€ข Execution: Malicious MCP server begins responding to model context
    requests, injecting or capturing payloads.
    โ€ข Infection/Persistence: Optional host-side agent or service persists
    to continue intercepting MCP traffic.
    โ€ข Exfiltration: Captured sensitive model inputs/outputs are
    transmitted to attacker-controlled exfiltration endpoints.
    โ€ข Cleanup/Cover Tracks: Logs may be modified or rotated to hide
    traffic patterns.

    Detection
    โ€ข Monitor for outbound connections to unknown MCP endpoints and
    unusual TLS/SNI values.
    โ€ข Inspect HTTP/2 or HTTP POST bodies used by MCP for anomalous fields
    or repetitive metadata that indicates exfiltration.
    โ€ข Implement network IDS/IPS rules to flag persistent connections to
    newly seen MCP hosts and unusual request/response sizes.
    โ€ข Correlate host process activity following MCP interactions (new
    services, unexpected file writes, child processes of model client
    processes).

    Mitigation
    โ€ข Enforce endpoint allowlisting and mutual TLS for MCP clients and servers.
    โ€ข Validate and cryptographically sign MCP server metadata and
    distribute it through trusted channels.
    โ€ข Harden CI/CD and supply-chain mechanisms that publish or register
    MCP endpoints.
    โ€ข Apply egress filtering and DLP controls on model input/output flows.

    References & notes

    The article is a Securelist research post; it documents a PoC and
    analysis but does not list CVEs or named threat actors. The insights
    should be integrated into model-serving security reviews and
    supply-chain risk assessments.

    ๐Ÿ”น MCP #supplychain #data_exfiltration #modelsecurity #MITRE_ATT&CK

    ๐Ÿ”— Source: securelist.com/model-context-p