← AVOID.NET
Entity Graph
Browse extracted entities, relationships, and potential duplicates.
Total entities
28,852
Relationships
32,017
Potential duplicates
2
Filter by kind
Potential Duplicates
Entities with similar names that may refer to the same thing. Use the merge API to combine them.
substring match♦ Clippy Token ($CLIPPY) — Microsoft X Account Hijack↔♦ Clippy Token ($CLIPPY) — Microsoft X Account Hijack Pump-and-Dumpb336c2ba / 90d84978
substring match↯ NEAR token fell approximately 7.5–8.93%, reaching a low of roughly $4.76.↔↯ NEAR Intents states the contract-side vulnerability has been patched, pledges full reimbursement, and reports the incident to law enforcement; deposits and withdrawals on 11 networks remain paused for roughly 12 additional hours.5ad350e2 / 45fd7698
Merge instructions
curl -X POST /api/graph/merge \
-H "Authorization: Bearer $ADMIN_TOKEN" \
-H "Content-Type: application/json" \
-d '{"keepId": "<entity-to-keep>", "mergeId": "<entity-to-remove>"}'Entities
◇9fc32d43
GyGYxT6XVwtAuEEVSn2V6YZ7bgkCxkjVzyWt8ogtpumpwallet
♦b336c2ba
Clippy Token ($CLIPPY) — Microsoft X Account Hijacktoken
↯be2c4658
Payy published a technical post-mortem attributing the exploit's root cause to a proving-system vulnerability in the Noir/Barretenberg verifier developed by Aztec.(2026-09-29:payy-network-noir-barretenberg-verifier-flaw-post-mortem)event
↯3a7baf1a
A GitHub security advisory and CVE (CVE-2026-48100) describing a soundness flaw in Payy's agg_agg aggregation circuit, patched in version 1.3.0, was published.(2026-09-28:payy-network-noir-barretenberg-verifier-flaw-post-mortem)event
↯08fd86c3
Payy stated it had completed initial root-cause analysis, ruled out a compromised key, social engineering, and off-chain infrastructure breach, and engaged a third-party audit firm to validate findings before publishing a full report.(2026-09-25:payy-network-noir-barretenberg-verifier-flaw-post-mortem)event
↯58c38d73
A second transaction several hours after the first drained a further approximately 90,202 USDC to the same receiving address, bringing the combined total to roughly $1.92 million.(2026-09-24:payy-network-noir-barretenberg-verifier-flaw-post-mortem)event
↯84e0ffb8
The Barretenberg fix was shipped in release v5.0.0; Payy's deployment, pinned to an older version, reportedly did not receive the patch and was not notified.(2026-07-13:payy-network-noir-barretenberg-verifier-flaw-post-mortem)event
↯530d08dc
Aztec reportedly fixed a missing boundary-opening check (A(1) = 0) in Barretenberg's small-subgroup IPA verifier, per Payy's post-mortem as summarized by a secondary source.(2026-05-14:payy-network-noir-barretenberg-verifier-flaw-post-mortem)event
⌂8091e2ee
Payy Network — Noir/Barretenberg Verifier Flaw Post-Mortemprotocol
↯01208f8a
Scammers deploy a counterfeit GIWA Layer 2 network using chain ID 9134, including a fraudulent cross-chain bridge. DYORSwap lists the fraudulent network. Approximately 767.65 ETH begins flowing in from roughly 1,335 addresses.(2026-09-26:dyorswap)event
↯d0c1c2d8
DYORSwap begins public activity; @DYORSWAPDEX Twitter/X account launches. Approximate date based on account activity records.(2024-01-01:dyorswap)event
⌂5f09cb71
DYORSwapprotocol
◎ba343a69
windowslatest.comdomain
↯72ecef6f
The impersonator account @clippymsftcto, which the hijacked Microsoft account had followed and reposted, is suspended by X.(2026-10-02:clippy-token-clippy-microsoft-x-account-hijack-pump-and-dump)event
◇42053b58
7eMJmn1bYWSQEwxAX7CyngBzGNGu1cT582asKxxRpumpwallet
♦90d84978
Clippy Token ($CLIPPY) — Microsoft X Account Hijack Pump-and-Dumptoken
◎4bf744f8
blog.openvpn.netdomain
◎277bfd3a
ctiacademy.iodomain
↯477a8098
CNBC published CEO Gracy Chen interview stating Bitget was 'not expecting to recover a lot' of the stolen funds. Full withdrawal resumption including P2P completed.(2026-10-02:bitget-hack-third-party-zero-day-vendor-unidentified-october-2026)event
↯81eb923f
DYORSWAP reports over 200 ETH paid out to affected users. A 40% compensation ratio is applied for addresses that bridged under 5 ETH; addresses over 5 ETH flagged for separate review. Official compensation address published: 0xdf25f88aa6cde9937fdcfcf10fa349528c79dbf9.(2026-09-28:dyorswap)event
↯4ff22b1d
GIWA publicly confirms its mainnet has not launched. DYORSwap issues an alert identifying the fake GIWA mainnet as fraudulent, confirms approximately 766.25 ETH (~$2 million) was drained from 1,335 addresses, and announces plans to compensate affected users from treasury funds.(2026-09-27:dyorswap)event
↯cd8c945e
DYORSWAP publishes a tiered compensation plan: a 40% reimbursement ratio for users who bridged less than 5 ETH, with larger amounts subject to individual review.(2026-09:dyorswap)event
⌂76fdcbf6
DYORSWAPprotocol
↯468bb51a
NEAR Intents confirmed full recovery of the $3.8 million in stolen funds; declared the incident resolved and halted further investigation.(2026-10-02:near-intents-omni-exploit-october-2026-3-8m)event
↯5ad350e2
NEAR token fell approximately 7.5–8.93%, reaching a low of roughly $4.76.(2026-10-01:near-intents-omni-exploit-october-2026-3-8m)event
↯dd582798
NEAR Intents blocked a $50 million swap attempt linked to the suspected Bitget hack perpetrators, freezing approximately $503,000.(2026-09-29:near-intents-omni-exploit-october-2026-3-8m)event
♦9e91a238
NEAR Intents Omni Exploit October 2026 ($3.8M)token
↯4630c780
Bitget confirmed publicly that a zero-day in unnamed third-party security products was the root cause; vendor identity remained undisclosed, and CEO Gracy Chen told CNBC the exchange was 'not expecting to recover a lot' of the stolen funds.(2026-10:bitget-hack-third-party-zero-day-vendor-unidentified-october-2026)event
↯decde71e
Bitget confirmed final loss figure of approximately $387.5 million after additional transaction reconciliation. Protection Fund replenished above $300 million. P2P withdrawals scheduled to resume October 2.(2026-09-30:bitget-hack-third-party-zero-day-vendor-unidentified-october-2026)event
↯406f12aa
Insurance Journal reported North Korea's 2026 crypto theft total surpassed $1 billion as a result of the Bitget hack.(2026-09-29:bitget-hack-third-party-zero-day-vendor-unidentified-october-2026)event
↯80a1bfa6
CEO disclosed attack details publicly, including that attackers used legitimate credentials and disguised activity as routine operations. ZachXBT published analysis identifying five alleged launderers. Phased withdrawal resumption began.(2026-09-28:bitget-hack-third-party-zero-day-vendor-unidentified-october-2026)event
↯cb1e0660
Bitget publicly disclosed the breach; initial loss estimate of $351.6 million reported. CEO Gracy Chen disclosed North Korea was 'very likely' responsible. Mandiant and SlowMist engaged for independent investigation.(2026-09-25:bitget-hack-third-party-zero-day-vendor-unidentified-october-2026)event
↯a9830718
19:05 UTC: Bitget's risk-control system automatically blocked withdrawals. 19:14 UTC: Highest-level emergency response activated.(2026-09-24:bitget-hack-third-party-zero-day-vendor-unidentified-october-2026)event
↯6861dd77
Similar hidden-script activity observed on two additional Product A nodes, according to SlowMist forensic timeline.(2026-09-23:bitget-hack-third-party-zero-day-vendor-unidentified-october-2026)event
↯0f4e0701
Earliest malicious activity identified in logs: a service on a Product A node was reportedly compromised via a zero-day vulnerability, allowing attacker access to environment variables including database credentials.(2026-08-31:bitget-hack-third-party-zero-day-vendor-unidentified-october-2026)event
⌂5b8ece23
Bitget Hack Third-Party Zero-Day Vendor (Unidentified, October 2026)protocol
↯b7f24adc
Multiple crypto news outlets publish full coverage. Incident is categorized as a third-party module exploit, not an Aave v3 or Safe infrastructure breach.(2026-10-02:flashloopadapter-aave-v3-safe-module-exploit)event
↯5773ac06
SlowMist issues public alert identifying the access control vulnerability and publishing attacker and contract addresses.(2026-10-01:flashloopadapter-aave-v3-safe-module-exploit)event
□2584f743
FlashLoopAdapter (Aave v3 Safe Module Exploit)organization
↯3ce2f90c
On-chain investigator ZachXBT reports the stolen funds were sent to KuCoin and bridged to Bitcoin; attacker identity remains unconfirmed.(2026-10:near-intents-omni-exploit-october-2026)event
↯45fd7698
NEAR Intents states the contract-side vulnerability has been patched, pledges full reimbursement, and reports the incident to law enforcement; deposits and withdrawals on 11 networks remain paused for roughly 12 additional hours.(2026-10-01:near-intents-omni-exploit-october-2026)event
↯11e368df
NEAR Intents reportedly blocks a roughly $50 million swap attempt and freezes over $500,000 linked to the attacker behind a separate ~$387.5-388 million theft from exchange Bitget, days before NEAR Intents' own exploit.(2026-09:near-intents-omni-exploit-october-2026)event
□b77f6354
NEAR Intents Omni Exploit (October 2026)organization
↯f05d045b
U.S. District Court entered default judgments against Brian Early and Alisha Ann Kingrey for $31.48 million ($15,732,455.40 restitution + $15,752,455 civil monetary penalty) and imposed permanent trading and registration bans, formally closing the CFTC enforcement action.(2026-09-30:rene-larralde-fundsz-founder)event
↯3bce5190
CFTC filed motion for default judgment against Brian Early and Alisha Ann Kingrey.(2026-08-18:rene-larralde-fundsz-founder)event
↯b241efbb
Court approved settlements with the Larralde estate (represented by widow Rachel Larralde) and Juan Pablo Valcarce. The estate surrendered a Rockledge, FL home, $4.1M in a bank account, and $2.67M in cryptocurrency. Valcarce received a permanent injunction with no monetary penalty.(2026-07-30:rene-larralde-fundsz-founder)event
↯555ee793
Rene Larralde died, age approximately 51, in Melbourne, Florida. The CFTC was informed of his death. Cause of death was not publicly reported.(2023-09-06:rene-larralde-fundsz-founder)event
Data refreshes every 5 minutes · All metrics derived from Supabase