CVE-2024-7014, known as EvilVideo, is a vulnerability in Telegram for Android that affects version 10.14.4 and earlier. The flaw allows an attacker to send a malicious Android application that is disguised as a video file through Telegram messages. The issue is in how the application presents or handles the received file, causing a malicious APK to appear to the recipient as if it were a benign video. This can facilitate social engineering and increase the likelihood that a user will interact with the file and proceed toward installation of the malicious application.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a proof-of-concept exploit for CVE-2024-7014 (EvilVideo) affecting Telegram for Android (versions 10.14.4 and earlier). The exploit consists of a Python script (Poc.py) that uses the pyTelegramBotAPI library to upload a malicious file (crafted HTML disguised as an MP4 video) to a Telegram channel. The malicious file (Poc_CVE_2024_7014.txt) contains HTML and JavaScript that immediately redirects the user to download a malicious APK from an attacker-controlled server (http://attacker-server.com/download/telegram-update.apk). The README provides setup instructions, including how to configure the bot, channel, and payload. The exploit leverages social engineering by making the file appear as a legitimate video update, complete with a thumbnail image, to entice users to open it and trigger the malware download. The repository structure is straightforward, with the main exploit logic in Poc.py, the payload in Poc_CVE_2024_7014.txt, and supporting documentation and images.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.