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

JBS

Ransomware

loading..
loading..
loading..

JBS disclosed ransom of $11 million equivalent cryptos to restore from ransomware attack

JBS said the buyback took place in bitcoins. private companies should not pay the ransom...

09-Jun-2021
3 min read

No content available.

Related Articles

loading..

Cloudflare

Cloudflare has made a decisive leap in secure communications by open-sourcing Or...

**Cloudflare Open-Sources Orange Meets: A Breakthrough for End-to-End Encrypted Group Video Calls** Cloudflare has made a decisive leap in secure communications by open-sourcing Orange Meets, its group video calling app now equipped with robust end-to-end encryption (E2EE) based on the Messaging Layer Security (MLS) protocol[1][2][3]. This move positions Orange Meets as a transparent, standards-driven alternative for privacy-conscious developers, researchers, and encryption enthusiasts. **A New Standard for Video Call Security** Unlike most group video platforms that rely on a central Selective Forwarding Unit (SFU)—which can potentially access unencrypted media—Orange Meets encrypts all audio and video entirely on the client side using MLS, an IETF-standardized group key exchange protocol[1][2][3]. This ensures that even Cloudflare’s own infrastructure cannot access call content, closing a major privacy gap in scalable video conferencing. **Technical Innovations: MLS and the Designated Committer Algorithm** Orange Meets leverages a Rust-based MLS implementation, compiled to WebAssembly for browser compatibility, to provide continuous group key agreement. This enables forward secrecy and post-compromise security, essential for dynamic environments where participants may join or leave at any time[1][4][2][3]. To securely manage these membership changes, Cloudflare introduced the “Designated Committer Algorithm”—a client-side protocol that designates a participant to handle cryptographic updates, verified for correctness using formal TLA+ modeling[1][4][2][3]. **Transparency and Trust by Design** Each session displays a unique “safety number” for participants to verify out-of-band, preventing man-in-the-middle attacks and boosting user confidence in the system’s integrity[2][3]. The entire E2EE implementation is open source, allowing independent scrutiny and adaptation by the broader community. **A Prototype, Not a Zoom Rival—Yet** Cloudflare is clear: Orange Meets is a technical showcase and not a consumer-ready rival to Zoom or Teams[4][2]. It lacks many enterprise features and hasn’t undergone extensive security audits. However, as a proof-of-concept, it sets a new bar for open, verifiable E2EE in group video calls and provides a modular foundation for future secure communication tools[4][2][3]. **Implications for the Future of Encrypted Communications** Orange Meets’ open, standards-based approach could accelerate adoption of MLS across the industry, offering a blueprint for privacy-first video platforms at a time when trust in centralized infrastructure is waning[4][2][3]. Developers can experiment with the live demo or deploy their own instance using the public codebase, marking a significant step forward for transparent, secure, and scalable group communications. In a landscape often dominated by proprietary black boxes, Cloudflare’s Orange Meets stands out as a bold experiment in cryptographic openness and user empowerment. [1] https://blog.cloudflare.com/orange-me2eets-we-made-an-end-to-end-encrypted-video-calling-app-and-it-was/ [2] https://www.bleepingcomputer.com/news/security/cloudflare-open-sources-orange-meets-with-end-to-end-encryption/ [3] https://cyberinsider.com/cloudflare-debuts-end-to-end-encrypted-video-chat-with-orange-meets-e2ee/ [4] https://hackyourmom.com/en/novyny/cloudflare-vidkryv-orange-meets-z-naskriznym-shyfruvannyam/ [5] https://github.com/cloudflare/orange [6] https://app.daily.dev/posts/orange-me2eets-we-made-an-end-to-end-encrypted-video-calling-app-and-it-was-easy-jjeztndwb [7] https://www.cloudflare.com/en-in/developer-platform/products/cloudflare-realtime/ [8] https://news.itsfoss.com/cloudflare-orange-me2eets/ [9] https://developers.cloudflare.com/realtime/changelog/ [10] https://www.bleepingcomputer.com/tag/orange-meets/

loading..   30-Jun-2025
loading..   3 min read
loading..

ADC

Citrix

New CitrixBleed 2 flaw lets hackers hijack NetScaler sessions. Patch now and ter...

A newly discovered vulnerability in Citrix NetScaler ADC and Gateway, dubbed "CitrixBleed 2," enables unauthenticated attackers to hijack user sessions by exploiting a flaw in out-of-bounds memory [read](https://support.citrix.com/support-home/kbsearch/article?articleNumber=CTX693420) (CVE-2025-5777). This critical issue enables attackers to access sensitive data—including session tokens and credentials—from memory, potentially bypassing multi-factor authentication and taking over user sessions on public-facing gateways and virtual servers. The flaw affects NetScaler devices configured as a Gateway (such as VPN virtual servers, ICA Proxy, Clientless VPN, RDP Proxy) or an AAA virtual server, and impacts versions before 14.1-43.56, 13.1-58.32, and certain FIPS/NDcPP releases. A related high-severity vulnerability (CVE-2025-5349) also affects the NetScaler Management Interface, but requires access to specific management IPs. Security experts warn that, similar to the original "CitrixBleed" flaw (CVE-2023-4966), attackers can replay stolen session tokens to hijack accounts even after patching—unless all active sessions are terminated after the update. Mandiant CTO Charles Carmakal emphasized that failure to terminate sessions after patching led to significant breaches, including nation-state espionage and ransomware attacks, during the 2023 incident. Citrix urges administrators to: - Immediately update to the latest supported versions (14.1-43.56, 13.1-58.32, or relevant FIPS releases) - Review and terminate all active ICA and PCoIP sessions after updating, using commands like `kill icaconnection -all` and `kill pcoipconnection -all` - Upgrade from end-of-life versions (such as ADC/Gateway 12.1 non-FIPS and 13.0), which will not receive patches. Over 56,500 NetScaler endpoints are currently exposed online, underscoring the urgency for organizations to patch and secure their systems against this new threat.

loading..   27-Jun-2025
loading..   2 min read
loading..

WhatsApp

US House bans WhatsApp from 12,000+ staff devices over spyware threats & cyberse...

The United States House of Representatives has taken a significant step in its cybersecurity measures by imposing a ban on WhatsApp across all government-issued devices. This move, announced on June 23, 2025, is not just a standalone decision but a part of a larger trend of increasing government technology restrictions. It marks a crucial point in the ongoing debate over messaging app security, data sovereignty, and the delicate balance between convenience and cybersecurity in government communications. ### Why was the WhatsaApp Ban imposed? The ban was officially communicated through a memo sent by House Chief Administrative Officer Catherine Szpindor to all House staff on Monday, June 23, 2025. The directive affects approximately 12,000 House employees and prohibits the use of WhatsApp on all government-managed devices, including smartphones, desktop computers, and web browsers. The memo explicitly stated that staff members “are NOT allowed to download or keep the WhatsApp application on any House device” and warned that those currently using the app would be contacted to remove it. The Office of Cybersecurity’s assessment categorized WhatsApp as a _“high risk to users due to the lack of transparency in how it protects user data, absence of stored data encryption, and potential security risks involved with its use. This technical evaluation formed the cornerstone of the decision, distinguishing it from previous app bans that were primarily motivated by concerns about foreign ownership. ### Emerging Security Concerns The House’s cybersecurity office identified six primary security concerns that justified the ban on WhatsApp. The most critical issues were classified as high-impact threats, including the lack of transparency in WhatsApp’s data protection practices and the absence of encryption for stored data. This distinction between end-to-end encryption for messages in transit and encryption for data at rest became a crucial technical point in the evaluation, as security concerns cited by the US House Office of Cybersecurity led to the ban of WhatsApp from government devices. The metadata collection practices of WhatsApp have emerged as a significant concern among cybersecurity experts and government officials. While WhatsApp’s messages are end-to-end encrypted, the platform collects extensive metadata, including communication patterns, timestamps, IP addresses, and contact information. Former NSA General Counsel Stewart Baker’s observation that “metadata tells you everything about somebody’s life” has become increasingly relevant in government cybersecurity discussions. An informational graphic detailing WhatsApp’s end-to-end encryption and the types of communication it secures. The security evaluation also highlighted WhatsApp’s integration with Meta’s broader ecosystem as a risk factor. The potential for data sharing between WhatsApp and other Meta companies, including Facebook and Instagram, raised concerns about data sovereignty and control over sensitive government communications. ### Paragon Spyware Connection A critical factor influencing the House’s decision was the January 2025 revelation that Israeli spyware company Paragon Solutions had targeted approximately 90 WhatsApp users, including journalists and civil society members. This incident, which WhatsApp characterized as a “zero-click” attack requiring no user interaction, highlighted the platform’s vulnerability to sophisticated state-sponsored surveillance. The Paragon campaign utilized malicious PDF files sent through WhatsApp groups to compromise targets across more than two dozen countries, primarily in Europe. Citizen Lab’s subsequent analysis in March 2025 revealed that Paragon’s Graphite spyware had been deployed by government customers in Australia, Canada, Cyprus, Denmark, Israel, and Singapore. The acquisition of Paragon by American private equity firm AE Industrial Partners for approximately $900 million in December 2024 added another layer of complexity to the security concerns. WhatsApp’s collaboration with Citizen Lab and its notification of potentially compromised users demonstrated the platform’s commitment to security transparency, yet also highlighted the ongoing vulnerabilities that sophisticated spyware operations could exploit. The incident provided concrete evidence of the security risks that the House’s cybersecurity office sought to mitigate through the ban. The House’s memo recommended five alternative messaging platforms: Microsoft Teams, Signal, Amazon Wickr, Apple’s iMessage, and FaceTime. This selection reveals the government’s prioritization of different security attributes and its willingness to accept varying levels of privacy protection across approved platforms. Signal emerged as the most privacy-focused option among the approved alternatives, offering end-to-end encryption, metadata protection, and open-source code transparency. The Signal Foundation’s non-profit structure and commitment to minimal data collection stood in stark contrast to the commercial messaging platforms on the approved list. However, Signal’s inclusion raised questions given its previous association with national security controversies, including the March 2025 incident where Pentagon officials inadvertently shared sensitive information about Yemen operations through a Signal group chat. Comparison chart detailing security and privacy features of popular peer-to-peer messaging apps, including WhatsApp, Signal, and iMessage. Microsoft Teams, despite lacking end-to-end encryption and metadata protection, received approval due to its enterprise-grade security controls and integration with government IT infrastructure. Amazon’s Wickr inclusion reflected the government’s acceptance of corporate-owned, yet security-focused platforms. At the same time, Apple’s iMessage and FaceTime represented a middle ground with end-to-end encryption but limited metadata protection. The WhatsApp ban represents the latest development in an accelerating pattern of government technology restrictions that began with the TikTok ban from House devices in December 2022. This precedent established the framework for evaluating foreign-owned applications and platforms that posed potential national security risks. The TikTok logo is displayed on a smartphone resting on a keyboard, symbolizing government policy bans on specific applications. The timeline of recent restrictions reveals an evolving government approach to cybersecurity threats. In 2024, [ChatGPT](https://www.secureblink.com/cyber-security-news/europe-looks-to-ukraine-for-the-future-of-defense-tech) faced restrictions, limited to paid versions only, due to concerns about AI safety. Microsoft Copilot received partial bans due to AI integration risks, while the Chinese AI platform DeepSeek faced proposed legislation for a complete ban following its rapid adoption by American users. Comprehensive analysis of the US House WhatsApp ban: timeline, security concerns, approved alternatives, and broader government cybersecurity policies. The pattern of restrictions demonstrates the House’s increasingly proactive approach to cybersecurity threats, moving beyond reactive measures to preventive policies. Chief Administrative Officer Catherine Szpindor’s leadership in implementing these restrictions reflects her extensive background in information technology and cybersecurity, including previous roles as Chief Information Officer and Director of Enterprise Applications. ### How Meta’s Responded to this WhatsApp Ban Meta responded to the House’s decision with strong disagreement, characterizing the ban as unjustified given WhatsApp’s security features. Company spokesperson Andy Stone emphasized that WhatsApp’s end-to-end encryption provides _“a higher level of security than most of the apps on the CAO’s approved list. Meta’s argument highlighted the technical distinction between message content encryption and the broader security concerns raised by the House’s cybersecurity office. The company’s response also noted the regular use of WhatsApp by House and Senate members, suggesting that the ban created an inconsistency between official policy and actual practice. Meta’s statement that it _“looks forward to ensuring members of the House can join their Senate counterparts in doing so officially”_ indicated the company’s intention to pursue policy reversal. The technology industry’s broader reaction reflected concerns about the precedent set by the ban and its potential impact on other platforms. The decision occurred amid Meta’s ongoing antitrust challenges with the Federal Trade Commission over its acquisitions of WhatsApp and Instagram, adding regulatory complexity to the cybersecurity concerns. ### Implications of WhatsApp Ban The WhatsApp ban illuminates several critical trends in government cybersecurity policy and the evolving relationship between technology platforms and national security. The decision represents a shift toward data sovereignty as a primary concern, prioritizing government control over communication infrastructure regardless of technical security measures. The emphasis on transparency requirements reflects the growing sophistication of governments in evaluating cybersecurity threats beyond simple encryption metrics. The House’s focus on metadata protection and data handling practices demonstrates an understanding that modern surveillance threats extend beyond message content to communication patterns and behavioral analysis. The ban also highlights the tension between federal cybersecurity recommendations and regulatory compliance. While the FBI and CISA have recommended the use of encrypted messaging for government officials to protect against telecommunications infrastructure compromises, the House’s decision prioritizes transparency and control over encryption alone. The international implications of the decision extend beyond immediate cybersecurity concerns to broader questions of digital sovereignty and platform governance. The selection of approved alternatives reflects preferences for platforms with clearer governance structures and more direct accountability to U.S. regulatory oversight, even when those platforms may offer fewer privacy protections than the banned application. The House of Representatives’ ban on WhatsApp represents a significant evolution in government cybersecurity policy, moving beyond concerns about foreign ownership to address transparency, data sovereignty, and sophisticated surveillance threats. The decision affects thousands of government employees while establishing new precedents for evaluating the security of messaging platforms in government contexts. The Paragon spyware incidents provided concrete evidence of the vulnerabilities that motivated the ban, while Meta’s strong opposition highlighted the ongoing tension between platform security claims and government oversight requirements. The selection of approved alternatives reveals a complex calculus balancing security features, transparency requirements, and practical governance considerations. As government cybersecurity policies continue to evolve, the WhatsApp ban serves as a critical case study in the challenges of securing government communications in an era of sophisticated state-sponsored surveillance and complex platform ecosystems. The decision’s long-term impact will depend on its effectiveness in improving government communication security while maintaining operational efficiency, as well as the broader precedent it establishes for future technology restrictions.

loading..   26-Jun-2025
loading..   9 min read