🟑 CVE-2025-4250: A vulnerability was found in c... 🟑 CVE-2025-4249: A vulnerability was found in P... 🟑 CVE-2025-4248: A vulnerability has been found... 🟑 CVE-2025-4247: A vulnerability, which was cla... ⚠️ CVE-2025-47245: In BlueWave Checkmate through ... ⚠️ CVE-2025-47244: Inedo ProGet through 2024.22 a... 🟑 CVE-2025-47241: In browser-use (aka Browser Us... 🟑 CVE-2025-4244: A vulnerability, which was cla... 🟑 CVE-2025-4243: A vulnerability, which was cla... 🟑 CVE-2025-4242: A vulnerability classified as ... 🟑 CVE-2025-1838: IBM Cloud Pak for Business Aut... 🟑 CVE-2025-4241: A vulnerability classified as ... 🟑 CVE-2025-4240: A vulnerability was found in P... 🟑 CVE-2025-4239: A vulnerability was found in P... 🟑 CVE-2025-4238: A vulnerability was found in P... 🟑 CVE-2025-1495: IBM Business Automation Workfl... 🟑 CVE-2024-41753: IBM Cloud Pak for Business Aut... 🟑 CVE-2025-4237: A vulnerability was found in P... 🟑 CVE-2025-4236: A vulnerability has been found... 🟑 CVE-2025-4226: A vulnerability classified as ... 🟑 CVE-2025-3815: The SurveyJS plugin for WordPr... 🟑 CVE-2025-4222: The Database Toolset plugin fo... 🟑 CVE-2025-4199: The Abundatrade Plugin plugin ... 🟑 CVE-2025-4198: The Alink Tap plugin for WordP... 🟑 CVE-2025-4188: The Advanced Reorder Image Tex... 🟑 CVE-2025-4172: The VerticalResponse Newslette... 🟑 CVE-2025-4170: The Xavin's Review Rating... 🟑 CVE-2025-4168: The Subpage List plugin for Wo... 🟒 CVE-2025-47229: libpspp-core.a in GNU PSPP thr... πŸ”₯ CVE-2025-3918: The Job Listings plugin for Wo... 🟑 CVE-2025-3779: The Personizely plugin for Wor... ⚠️ CVE-2024-13738: The The Motors - Car Dealer, R... ⚠️ CVE-2025-46723: OpenVM is a performant and mod... 🟑 CVE-2025-21572: OpenGrok 1.13.25 has a reflect... ⚠️ CVE-2022-21546: In newer version of the SBC sp... 🟑 CVE-2025-4218: A vulnerability was found in h... 🟒 CVE-2025-4215: A vulnerability was found in g... 🟑 CVE-2025-47226: Grokability Snipe-IT before 8.... πŸ”₯ CVE-2025-0782: A vulnerability in the S3 buck... 🟑 CVE-2025-4214: A vulnerability was found in P... 🟒 CVE-2024-58253: In the obfstr crate before 0.4... 🟑 CVE-2025-4213: A vulnerability has been found... 🟑 CVE-2025-46332: Flags SDK is an open-source fe... 🟑 CVE-2025-3879: Vault Community, Vault Enterpr... 🟑 CVE-2025-4210: A vulnerability classified as ... 🟑 CVE-2025-4166: Vault Community and Vault Ente... ⚠️ CVE-2025-1884: Use-After-Free vulnerability e... ⚠️ CVE-2025-1883: Out-Of-Bounds Write vulnerabil... ⚠️ CVE-2025-4204: The Ultimate Auction Pro plugi... πŸ”₯ CVE-2025-2605: Improper Neutralization of Spe... 🟑 CVE-2025-2488: Improper Neutralization of Inp... ⚠️ CVE-2025-2421: Improper Control of Generation... ⚠️ CVE-2025-1301: Improper Neutralization of Inp... πŸ”₯ CVE-2025-2812: Improper Neutralization of Spe... 🟑 CVE-2024-11142: Cross-Site Request Forgery (CS... 🟑 CVE-2024-13860: The Buddyboss Platform plugin ... 🟑 CVE-2024-13859: The Buddyboss Platform plugin ... 🟑 CVE-2024-13858: The Buddyboss Platform plugin ... 🟑 CVE-2025-47201: In Intrexx Portal Server befor... 🟑 CVE-2025-3488: The WPML plugin for WordPress ... 🟑 CVE-2025-3438: The MStore API – Create Native... 🟑 CVE-2025-3858: The Formality plugin for WordP... 🟑 CVE-2025-3748: The Taxonomy Chain Menu plugin... πŸ”₯ CVE-2025-3709: Agentflow from Flowring Techno... πŸ”₯ CVE-2025-3708: Le-show medical practice manag... 🟑 CVE-2025-3707: The eHDR CTMS from Sunnet has ... 🟑 CVE-2025-3510: The tagDiv Composer plugin for... 🟑 CVE-2025-1327: The Homey theme for WordPress ... 🟑 CVE-2025-1326: The Homey theme for WordPress ... 🟑 CVE-2024-13420: Multiple plugins and/or themes... 🟑 CVE-2024-13419: Multiple plugins and/or themes... ⚠️ CVE-2024-13418: Multiple plugins and/or themes... ⚠️ CVE-2024-13344: The Advance Seat Reservation M... ⚠️ CVE-2024-13322: The Ads Pro Plugin - Multi-Pur... 🟑 CVE-2024-12023: The FULL – Cliente plugin for ... ⚠️ CVE-2025-4179: The Flynax Bridge plugin for W... 🟑 CVE-2025-4177: The Flynax Bridge plugin for W... 🟑 CVE-2025-4131: The GmapsMania plugin for Word... πŸ”₯ CVE-2025-3746: The OTP-less one tap Sign in p... 🟑 CVE-2025-3670: The KiwiChat NextClient plugin... 🟑 CVE-2025-2880: The Yame | Link In Bio plugin ... 🟑 CVE-2025-4197: A vulnerability classified as ... 🟑 CVE-2025-4196: A vulnerability was found in S... 🟑 CVE-2025-29825: User interface (ui) misreprese... 🟑 CVE-2025-4195: A vulnerability was found in i... 🟑 CVE-2025-4193: A vulnerability was found in i... 🟑 CVE-2025-4192: A vulnerability was found in i... 🟑 CVE-2024-55913: IBM Concert Software 1.0.0 thr... 🟑 CVE-2024-55912: IBM Concert Software 1.0.0 thr... 🟑 CVE-2024-55910: IBM Concert Software 1.0.0 thr... 🟑 CVE-2024-55909: IBM Concert Software 1.0.0 thr... 🟑 CVE-2025-4191: A vulnerability has been found... 🟑 CVE-2025-4186: A vulnerability, which was cla... 🟑 CVE-2025-4185: A vulnerability, which was cla... 🟑 CVE-2025-4184: A vulnerability classified as ... 🟑 CVE-2025-4183: A vulnerability classified as ... 🟑 CVE-2025-4182: A vulnerability was found in P... 🟑 CVE-2025-4181: A vulnerability was found in P... 🟑 CVE-2024-52903: IBM Db2 for Linux, UNIX and Wi... 🟑 CVE-2025-4180: A vulnerability was found in P...
The $308 Million Bitcoin Heist: A Deep Dive into the DMM Bitcoin Hack

The $308 Million Bitcoin Heist: A Deep Dive into the DMM Bitcoin Hack

In May 2024, the cryptocurrency world was rocked by a massive security breach involving DMM Bitcoin, a prominent Japanese crypto exchange. Hackers managed to siphon off 4,502.9 Bitcoin, valued at approximately $308 million at the time, marking one of the largest crypto heists in recent history.

The Attack Unveiled

The breach was detected on May 31, 2024, when DMM Bitcoin reported an "unauthorized leak" of Bitcoin from its wallets. The company promptly suspended several services, including Bitcoin withdrawals, spot trading, and the opening of new leveraged positions, to prevent further losses. Despite the severity of the attack, DMM Bitcoin assured its users that all customer deposits would be fully reimbursed, complying with Japanese regulations that mandate the separation of corporate and user funds.

Modus Operandi: Social Engineering at Play

Investigations by the U.S. Federal Bureau of Investigation (FBI) and the National Police Agency of Japan revealed that the perpetrators employed sophisticated social engineering tactics. In March 2024, an employee at Ginco, a Japanese cryptocurrency wallet software company, was approached by an individual posing as a recruiter on LinkedIn. Under the guise of a pre-employment test, the employee was persuaded to download a malicious Python script hosted on GitHub. This script compromised the employee's system, granting the attackers unauthorized access to Ginco's wallet management infrastructure.

By mid-May, the hackers exploited session cookies to impersonate the compromised employee, enabling them to infiltrate Ginco's unencrypted communication systems. This access allowed them to manipulate legitimate transaction requests, culminating in the unauthorized transfer of 4,502.9 Bitcoin from DMM Bitcoin's reserves.

Attribution to North Korean Actors

The FBI and Japanese authorities have attributed the heist to a North Korean cybercrime group known as "TraderTraitor," also referred to as Jade Sleet, UNC4899, and Slow Pisces. This group has a notorious history of targeting entities within the cryptocurrency sector, often employing social engineering techniques to infiltrate organizations and deploy malware-laden cryptocurrency applications.

Aftermath and Industry Implications

In the wake of the attack, DMM Bitcoin announced its decision to cease operations, citing the insurmountable impact of the breach. This incident underscores the persistent vulnerabilities within the cryptocurrency ecosystem, particularly concerning social engineering attacks that exploit human factors rather than technical flaws.

As of December 2024, the cryptocurrency industry has suffered losses exceeding $1.5 billion due to hacking incidents, reflecting a 17% decrease from the previous year. Nonetheless, the DMM Bitcoin heist serves as a stark reminder of the evolving tactics employed by cybercriminals and the imperative for robust security measures and heightened vigilance within the crypto community.

Conclusion

The $308 million theft from DMM Bitcoin highlights the critical need for comprehensive security protocols that encompass both technological defenses and employee awareness training. As cyber threats continue to evolve, the cryptocurrency industry must adopt a proactive stance to safeguard assets and maintain user trust in an increasingly digital financial landscape.

Sources

Back to Posts