logo
Overkill Security  Because Nothing Says 'Security' Like a Dozen Firewalls and a Biometric Scanner
О проекте Просмотр Уровни подписки Фильтры Обновления проекта Контакты Поделиться Метки
Все проекты
О проекте
A blog about all things techy! Not too much hype, just a lot of cool analysis and insight from different sources.

📌Not sure what level is suitable for you? Check this explanation https://sponsr.ru/overkill_security/55291/Paid_Content/

QA — directly or via email overkill_qa@outlook.com
Публикации, доступные бесплатно
Уровни подписки
Единоразовый платёж

Your donation fuels our mission to provide cutting-edge cybersecurity research, in-depth tutorials, and expert insights. Support our work today to empower the community with even more valuable content.

*no refund, no paid content

Помочь проекту
Regular Reader 1 500₽ месяц 16 200₽ год
(-10%)
При подписке на год для вас действует 10% скидка. 10% основная скидка и 0% доп. скидка за ваш уровень на проекте Overkill Security

Ideal for regular readers who are interested in staying informed about the latest trends and updates in the cybersecurity world without.

Оформить подписку
Pro Reader 3 000₽ месяц 30 600₽ год
(-15%)
При подписке на год для вас действует 15% скидка. 15% основная скидка и 0% доп. скидка за ваш уровень на проекте Overkill Security

Designed for IT professionals, cybersecurity experts, and enthusiasts who seek deeper insights and more comprehensive resources. + Q&A

Оформить подписку
Фильтры
Обновления проекта
Контакты
Поделиться
Метки
Читать: 2+ мин
logo Overkill Security

Abusing WSUS with MITM to perform ADCS ESC8 attack

This ‎article serves‏ ‎as ‎a ‎technical ‎guide ‎on‏ ‎how ‎a‏ ‎combination‏ ‎of ‎network ‎sniffing,‏ ‎MITM ‎attacks,‏ ‎and ‎exploitation ‎of ‎ADCS‏ ‎can‏ ‎lead ‎to‏ ‎significant ‎security‏ ‎breaches, ‎emphasizing ‎the ‎need ‎for‏ ‎robust‏ ‎security ‎measures‏ ‎in ‎network‏ ‎configurations ‎and ‎certificate ‎handling ‎processes.

📌WSUS‏ ‎Configuration‏ ‎and‏ ‎Vulnerability: ‎The‏ ‎article ‎details‏ ‎how ‎a‏ ‎Windows‏ ‎Server ‎Update‏ ‎Services ‎(WSUS) ‎server, ‎configured ‎to‏ ‎work ‎over‏ ‎HTTP,‏ ‎can ‎be ‎exploited.‏ ‎The ‎WSUS‏ ‎server’s ‎protocol ‎configuration ‎is‏ ‎accessible‏ ‎by ‎querying‏ ‎a ‎specific‏ ‎registry ‎key. ‎This ‎setup ‎allows‏ ‎for‏ ‎the ‎potential‏ ‎sniffing ‎of‏ ‎traffic ‎using ‎tools ‎like ‎Wireshark,‏ ‎which‏ ‎can‏ ‎capture ‎the‏ ‎communication ‎between‏ ‎clients ‎and‏ ‎the‏ ‎WSUS ‎server.

📌MITM‏ ‎Attack ‎Execution: ‎The ‎core ‎of‏ ‎the ‎attack‏ ‎involves‏ ‎a ‎Man-in-the-Middle ‎(MITM)‏ ‎approach ‎where‏ ‎an ‎attacker ‎intercepts ‎and‏ ‎relays‏ ‎requests ‎from‏ ‎a ‎client‏ ‎machine ‎to ‎the ‎WSUS ‎server.‏ ‎During‏ ‎this ‎process,‏ ‎the ‎attacker‏ ‎can ‎manipulate ‎the ‎communication ‎to‏ ‎redirect‏ ‎requests‏ ‎to ‎a‏ ‎rogue ‎server‏ ‎or ‎manipulate‏ ‎the‏ ‎responses.

📌ADCS ‎ESC8‏ ‎Exploit: ‎The ‎intercepted ‎communication ‎is‏ ‎then ‎used‏ ‎to‏ ‎facilitate ‎an ‎Active‏ ‎Directory ‎Certificate‏ ‎Services ‎(ADCS) ‎ESC8 ‎attack.‏ ‎This‏ ‎involves ‎relaying‏ ‎the ‎intercepted‏ ‎requests ‎to ‎a ‎Certificate ‎Authority‏ ‎web‏ ‎enrollment ‎page‏ ‎to ‎request‏ ‎a ‎certificate ‎using ‎a ‎compromised‏ ‎computer’s‏ ‎credentials.‏ ‎Successfully ‎executing‏ ‎this ‎attack‏ ‎can ‎allow‏ ‎the‏ ‎attacker ‎to‏ ‎obtain ‎unauthorized ‎certificates ‎that ‎can‏ ‎be ‎used‏ ‎for‏ ‎further ‎attacks ‎within‏ ‎the ‎network.

📌Toolset: PKINITtools‏ ‎and ‎scripts ‎for ‎manipulating‏ ‎Kerberos‏ ‎tickets ‎and‏ ‎exporting ‎them‏ ‎for ‎use ‎in ‎the ‎attack‏ ‎help‏ ‎in ‎extracting‏ ‎and ‎utilizing‏ ‎the ‎credentials ‎from ‎the ‎intercepted‏ ‎traffic‏ ‎to‏ ‎authenticate ‎against‏ ‎the ‎ADCS‏ ‎and ‎request‏ ‎certificates.

📌Security‏ ‎Implications ‎and‏ ‎Recommendations: The ‎attack ‎demonstrates ‎a ‎significant‏ ‎security ‎risk‏ ‎in‏ ‎using ‎unsecured ‎protocols‏ ‎(HTTP) ‎for‏ ‎critical ‎infrastructure ‎like ‎WSUS‏ ‎and‏ ‎ADCS. ‎The‏ ‎article ‎suggests‏ ‎that ‎securing ‎these ‎communications ‎using‏ ‎HTTPS‏ ‎and ‎implementing‏ ‎strict ‎access‏ ‎controls ‎and ‎monitoring ‎could ‎mitigate‏ ‎such‏ ‎attacks.

Читать: 2+ мин
logo Overkill Security

TeleTracker

TeleTracker offers ‎a‏ ‎suite ‎of ‎tools ‎for ‎threat‏ ‎intelligence ‎analysis,‏ ‎focusing‏ ‎on ‎Telegram ‎channels‏ ‎used ‎for‏ ‎malicious ‎purposes. ‎Its ‎features‏ ‎facilitate‏ ‎the ‎monitoring‏ ‎and ‎disruption‏ ‎of ‎active ‎malware ‎campaigns, ‎making‏ ‎it‏ ‎a ‎valuable‏ ‎resource ‎for‏ ‎cybersecurity ‎professionals. ‎These ‎scripts ‎are‏ ‎particularly‏ ‎useful‏ ‎for ‎threat‏ ‎intelligence ‎analysts‏ ‎or ‎researchers‏ ‎aiming‏ ‎to ‎monitor,‏ ‎collect, ‎and ‎track ‎adversaries ‎using‏ ‎Telegram ‎for‏ ‎command‏ ‎and ‎control ‎(C2)‏ ‎communications.

Features

📌View ‎Channel‏ ‎Messages ‎& ‎Download ‎Content:‏ ‎Allows‏ ‎users ‎to‏ ‎view ‎messages‏ ‎within ‎a ‎channel ‎and ‎download‏ ‎content‏ ‎directly ‎to‏ ‎a ‎newly‏ ‎created ‎'downloads' ‎folder ‎in ‎the‏ ‎current‏ ‎working‏ ‎directory. ‎It‏ ‎supports ‎the‏ ‎download ‎of‏ ‎various‏ ‎file ‎types‏ ‎including ‎documents, ‎photos, ‎and ‎videos.

📌Send‏ ‎Documents ‎via‏ ‎Telegram:‏ ‎Users ‎can ‎optionally‏ ‎send ‎messages‏ ‎and ‎documents ‎through ‎Telegram,‏ ‎supporting‏ ‎all ‎Telegram‏ ‎file ‎types‏ ‎with ‎auto-detection ‎of ‎MIME ‎type.

📌Message‏ ‎Selection:‏ ‎Provides ‎the‏ ‎option ‎to‏ ‎select ‎a ‎specified ‎number ‎of‏ ‎messages‏ ‎or‏ ‎a ‎specific‏ ‎message_id ‎for‏ ‎download, ‎with‏ ‎downloads‏ ‎always ‎occurring‏ ‎from ‎the ‎newest ‎to ‎the‏ ‎oldest ‎message.

📌Log‏ ‎Saving:‏ ‎Saves ‎logs ‎in‏ ‎a ‎pretty‏ ‎text ‎format ‎with ‎basic‏ ‎information‏ ‎under ‎a‏ ‎file ‎named‏ ‎<bot_name>.txt.

Usage

📌To ‎send ‎a ‎message ‎to‏ ‎a‏ ‎Telegram ‎channel,‏ ‎use ‎the‏ ‎command: ‎python ‎http://TeleTexter.py -t ‎YOUR_BOT_TOKEN ‎-c‏ ‎YOUR_CHAT_ID‏ ‎-m‏ ‎«Your ‎message‏ ‎here»

📌For ‎continuous‏ ‎message ‎sending‏ ‎(spamming),‏ ‎add ‎the‏ ‎--spam ‎flag ‎to ‎the ‎command.

http://📌TeleViewer.py is‏ ‎the ‎latest‏ ‎tool‏ ‎allowing ‎users ‎to‏ ‎view ‎and‏ ‎download ‎all ‎messages ‎and‏ ‎media‏ ‎from ‎a‏ ‎threat ‎actor-controlled‏ ‎Telegram ‎channel. ‎This ‎feature ‎can‏ ‎be‏ ‎accessed ‎by‏ ‎selecting ‎the‏ ‎number ‎6 ‎from ‎the ‎initial‏ ‎menu‏ ‎after‏ ‎running ‎http://TeleGatherer.py.

Читать: 1+ мин
logo Overkill Security

FBI IC3

Attackers ‎are‏ ‎employing ‎a ‎variety ‎of ‎methods,‏ ‎including ‎phishing‏ ‎emails‏ ‎with ‎malicious ‎attachments,‏ ‎obfuscated ‎script‏ ‎files, ‎and ‎Guloader ‎PowerShell,‏ ‎to‏ ‎infiltrate ‎and‏ ‎compromise ‎victim‏ ‎systems. ‎Invoice ‎fraud, ‎a ‎form‏ ‎of‏ ‎business ‎email‏ ‎compromise ‎(BEC),‏ ‎is ‎one ‎of ‎the ‎popular‏ ‎methods‏ ‎used‏ ‎by ‎attackers‏ ‎to ‎deceive‏ ‎victims. ‎In‏ ‎this‏ ‎type ‎of‏ ‎scam, ‎a ‎third ‎party ‎requests‏ ‎payment ‎fraudulently,‏ ‎often‏ ‎by ‎impersonating ‎a‏ ‎legitimate ‎vendor

Invoice‏ ‎scams ‎pose ‎a ‎significant‏ ‎threat‏ ‎to ‎businesses,‏ ‎as ‎they‏ ‎can ‎result ‎in ‎substantial ‎financial‏ ‎losses‏ ‎and ‎irreparable‏ ‎damage. ‎According‏ ‎to ‎the ‎FBI ‎IC3 ‎report,‏ ‎in‏ ‎2022,‏ ‎BEC ‎attacks‏ ‎caused ‎$2.7‏ ‎billion ‎in‏ ‎losses‏ ‎to ‎US‏ ‎victims, ‎making ‎it ‎the ‎most‏ ‎pervasive ‎form‏ ‎of‏ ‎business ‎email ‎compromise.

Some‏ ‎indicators ‎of‏ ‎fraudulent ‎email ‎invoices ‎include‏ ‎requests‏ ‎for ‎personally‏ ‎identifiable ‎information‏ ‎(PII), ‎unusual ‎requests ‎such ‎as‏ ‎changes‏ ‎to ‎banking‏ ‎or ‎payment‏ ‎information, ‎and ‎invoices ‎with ‎unusual‏ ‎dollar‏ ‎amounts.‏ ‎Additionally, ‎attackers‏ ‎often ‎use‏ ‎obfuscation ‎techniques‏ ‎to‏ ‎evade ‎defenses‏ ‎and ‎make ‎their ‎malicious ‎activities‏ ‎more ‎difficult‏ ‎to‏ ‎detect.

Читать: 2+ мин
logo Overkill Security

TA547 phishing campaign

The ‎TA547‏ ‎phishing ‎campaign ‎using ‎the ‎Rhadamanthys‏ ‎stealer ‎represents‏ ‎a‏ ‎significant ‎evolution ‎in‏ ‎cybercriminal ‎tactics,‏ ‎notably ‎through ‎the ‎integration‏ ‎of‏ ‎AI-generated ‎scripts.‏ ‎This ‎development‏ ‎serves ‎as ‎a ‎critical ‎reminder‏ ‎for‏ ‎organizations ‎to‏ ‎continuously ‎update‏ ‎and ‎adapt ‎their ‎cybersecurity ‎strategies‏ ‎to‏ ‎counter‏ ‎sophisticated ‎and‏ ‎evolving ‎threats.

Key‏ ‎Details ‎of‏ ‎the‏ ‎Attack

📌Impersonation ‎and‏ ‎Email ‎Content: ‎The ‎phishing ‎emails‏ ‎were ‎crafted‏ ‎to‏ ‎impersonate ‎the ‎German‏ ‎company ‎Metro‏ ‎AG, ‎presenting ‎themselves ‎as‏ ‎invoice-related‏ ‎communications. ‎These‏ ‎emails ‎contained‏ ‎a ‎password-protected ‎ZIP ‎file, ‎which‏ ‎when‏ ‎opened, ‎triggered‏ ‎a ‎remote‏ ‎PowerShell ‎script

📌Execution ‎Method: ‎The ‎PowerShell‏ ‎script‏ ‎executed‏ ‎directly ‎in‏ ‎memory, ‎deploying‏ ‎the ‎Rhadamanthys‏ ‎stealer‏ ‎without ‎writing‏ ‎to ‎the ‎disk. ‎This ‎method‏ ‎helps ‎avoid‏ ‎detection‏ ‎by ‎traditional ‎antivirus‏ ‎software

📌Use ‎of‏ ‎AI ‎in ‎Malware ‎Creation:‏ ‎There‏ ‎is ‎a‏ ‎strong ‎indication‏ ‎that ‎the ‎PowerShell ‎script ‎was‏ ‎generated‏ ‎or ‎at‏ ‎least ‎refined‏ ‎using ‎a ‎large ‎language ‎model‏ ‎(LLM).‏ ‎The‏ ‎script ‎featured‏ ‎grammatically ‎correct‏ ‎and ‎highly‏ ‎specific‏ ‎comments, ‎which‏ ‎is ‎atypical ‎for ‎human-generated ‎malware‏ ‎scripts

Evolving ‎Tactics‏ ‎and‏ ‎Techniques

📌Innovative ‎Lures ‎and‏ ‎Delivery ‎Methods:‏ ‎The ‎campaign ‎also ‎experimented‏ ‎with‏ ‎new ‎phishing‏ ‎tactics, ‎such‏ ‎as ‎voice ‎message ‎notifications ‎and‏ ‎SVG‏ ‎image ‎embedding,‏ ‎to ‎enhance‏ ‎the ‎effectiveness ‎of ‎credential ‎harvesting‏ ‎attacks

📌AI‏ ‎and‏ ‎Cybercrime: ‎The‏ ‎use ‎of‏ ‎AI ‎technologies‏ ‎like‏ ‎ChatGPT ‎or‏ ‎CoPilot ‎in ‎scripting ‎the ‎malware‏ ‎indicates ‎a‏ ‎significant‏ ‎shift ‎in ‎cybercrime‏ ‎tactics, ‎suggesting‏ ‎that ‎cybercriminals ‎are ‎increasingly‏ ‎leveraging‏ ‎AI ‎to‏ ‎refine ‎their‏ ‎attack ‎methods

📌Broader ‎Implications: ‎This ‎campaign‏ ‎not‏ ‎only ‎highlights‏ ‎the ‎adaptability‏ ‎and ‎technical ‎sophistication ‎of ‎TA547‏ ‎but‏ ‎also‏ ‎underscores ‎the‏ ‎broader ‎trend‏ ‎of ‎cybercriminals‏ ‎integrating‏ ‎AI ‎tools‏ ‎into ‎their ‎operations. ‎This ‎integration‏ ‎could ‎potentially‏ ‎lead‏ ‎to ‎more ‎effective‏ ‎and ‎harder-to-detect‏ ‎cyber ‎threats

Recommendations ‎for ‎Defense

📌Employee‏ ‎Training: Organizations‏ ‎should ‎enhance‏ ‎their ‎cybersecurity‏ ‎defenses ‎by ‎training ‎employees ‎to‏ ‎recognize‏ ‎phishing ‎attempts‏ ‎and ‎suspicious‏ ‎email ‎content

📌Technical ‎Safeguards: ‎Implementing ‎strict‏ ‎group‏ ‎policies‏ ‎to ‎restrict‏ ‎traffic ‎from‏ ‎unknown ‎sources‏ ‎and‏ ‎ad ‎networks‏ ‎can ‎help ‎protect ‎endpoints ‎from‏ ‎such ‎attacks

📌Behavior-Based‏ ‎Detection: Despite‏ ‎the ‎use ‎of‏ ‎AI ‎in‏ ‎crafting ‎attacks, ‎behavior-based ‎detection‏ ‎mechanisms‏ ‎remain ‎effective‏ ‎in ‎identifying‏ ‎and ‎mitigating ‎such ‎threats

Читать: 2+ мин
logo Overkill Security

Vulnerabilities in LG’s WebOS / LG SmartTV

Security ‎researchers‏ ‎from ‎Bitdefender ‎have ‎identified ‎multiple‏ ‎vulnerabilities ‎in‏ ‎LG’s‏ ‎WebOS, ‎affecting ‎various‏ ‎models ‎of‏ ‎the ‎company’s ‎smart ‎TVs.‏ ‎These‏ ‎vulnerabilities, ‎if‏ ‎exploited, ‎could‏ ‎allow ‎attackers ‎to ‎gain ‎unauthorized‏ ‎root‏ ‎access ‎to‏ ‎the ‎devices.

Affected‏ ‎Versions ‎and ‎Models:

📌The ‎vulnerabilities ‎impact‏ ‎LG‏ ‎TVs‏ ‎running ‎WebOS‏ ‎versions ‎4.9.7‏ ‎to ‎7.3.1‏ ‎across‏ ‎models ‎such‏ ‎as ‎LG43UM7000PLA, ‎OLED55CXPUA, ‎OLED48C1PUB, ‎and‏ ‎OLED55A23LA

Specific ‎Vulnerabilities:

📌CVE-2023-6317:‏ ‎Allows‏ ‎attackers ‎to ‎bypass‏ ‎PIN ‎verification‏ ‎and ‎add ‎a ‎privileged‏ ‎user‏ ‎profile ‎without‏ ‎user ‎interaction

📌CVE-2023-6318:‏ ‎Enables ‎attackers ‎to ‎elevate ‎their‏ ‎privileges‏ ‎and ‎gain‏ ‎root ‎access

📌CVE-2023-6319: Permits‏ ‎operating ‎system ‎command ‎injection ‎by‏ ‎manipulating‏ ‎a‏ ‎library ‎for‏ ‎displaying ‎music‏ ‎lyrics

📌CVE-2023-6320: Allows ‎for‏ ‎the‏ ‎injection ‎of‏ ‎authenticated ‎commands ‎by ‎exploiting ‎the‏ ‎com.webos.service.connectionmanager/tv/setVlanStaticAddress ‎API‏ ‎endpoint

Discovery‏ ‎and ‎Reporting:

📌These ‎vulnerabilities‏ ‎were ‎discovered‏ ‎by ‎Bitdefender ‎in ‎November‏ ‎2023‏ ‎and ‎reported‏ ‎to ‎LG,‏ ‎which ‎subsequently ‎released ‎patches ‎on‏ ‎March‏ ‎22, ‎2024

Scope‏ ‎of ‎Impact:

📌Over‏ ‎91,000 ‎devices ‎have ‎been ‎identified‏ ‎as‏ ‎potentially‏ ‎vulnerable. ‎These‏ ‎devices ‎are‏ ‎primarily ‎located‏ ‎in‏ ‎South ‎Korea,‏ ‎Hong ‎Kong, ‎the ‎US, ‎Sweden,‏ ‎and ‎Finland

Mitigation‏ ‎and‏ ‎User ‎Action:

📌LG ‎has‏ ‎released ‎patches‏ ‎for ‎these ‎vulnerabilities, ‎which‏ ‎are‏ ‎available ‎through‏ ‎the ‎TV’s‏ ‎settings ‎menu ‎under ‎Software ‎Update

📌Users‏ ‎are‏ ‎advised ‎to‏ ‎enable ‎automatic‏ ‎software ‎updates ‎to ‎ensure ‎their‏ ‎devices‏ ‎receive‏ ‎the ‎latest‏ ‎security ‎patches

Potential‏ ‎Risks:

📌If ‎exploited,‏ ‎these‏ ‎vulnerabilities ‎could‏ ‎allow ‎attackers ‎to ‎take ‎control‏ ‎of ‎the‏ ‎TV,‏ ‎access ‎sensitive ‎user‏ ‎data, ‎and‏ ‎potentially ‎use ‎the ‎compromised‏ ‎device‏ ‎as ‎part‏ ‎of ‎a‏ ‎botnet ‎or ‎for ‎other ‎malicious‏ ‎activities

Security‏ ‎Recommendations:

📌Besides ‎applying‏ ‎the ‎latest‏ ‎firmware ‎updates, ‎users ‎should ‎use‏ ‎strong,‏ ‎unique‏ ‎passwords ‎for‏ ‎their ‎devices‏ ‎and ‎secure‏ ‎their‏ ‎Wi-Fi ‎networks‏ ‎to ‎further ‎reduce ‎the ‎risk‏ ‎of ‎exploitation

Читать: 2+ мин
logo Overkill Security

BatBadBut

📌Vulnerability ‎Identification:‏ ‎The ‎critical ‎security ‎vuln ‎is‏ ‎identified ‎as‏ ‎«BatBadBut»‏ ‎and ‎is ‎tracked‏ ‎under ‎CVE-2024-24576

📌Affected‏ ‎Software: The ‎vuln ‎exists ‎in‏ ‎the‏ ‎Rust ‎standard‏ ‎library ‎and‏ ‎specifically ‎affects ‎Windows ‎systems

📌Severity ‎Rating: It‏ ‎has‏ ‎been ‎given‏ ‎the ‎highest‏ ‎severity ‎rating ‎with ‎CVSS ‎score‏ ‎of‏ ‎10.0,‏ ‎indicating ‎maximum‏ ‎severity

📌Vulnerability ‎Details: The‏ ‎flaw ‎arises‏ ‎from‏ ‎the ‎Rust‏ ‎standard ‎library ‎not ‎properly ‎escaping‏ ‎arguments ‎when‏ ‎invoking‏ ‎batch ‎files ‎on‏ ‎Windows ‎using‏ ‎the ‎Command ‎API. ‎This‏ ‎could‏ ‎allow ‎an‏ ‎attacker ‎to‏ ‎execute ‎arbitrary ‎shell ‎commands ‎by‏ ‎bypassing‏ ‎the ‎escaping

📌Conditions‏ ‎for ‎Exploitation: Successful‏ ‎exploitation ‎requires ‎specific ‎conditions: ‎execution‏ ‎of‏ ‎a‏ ‎command ‎on‏ ‎Windows, ‎the‏ ‎command ‎does‏ ‎not‏ ‎specify ‎the‏ ‎file ‎extension ‎or ‎uses ‎.bat‏ ‎or ‎.cmd,‏ ‎the‏ ‎command ‎contains ‎user-controlled‏ ‎input ‎as‏ ‎part ‎of ‎the ‎command‏ ‎arguments,‏ ‎and ‎the‏ ‎runtime ‎fails‏ ‎to ‎escape ‎the ‎command ‎arguments‏ ‎properly‏ ‎for ‎cmd.exe

📌Affected‏ ‎Versions: All ‎versions‏ ‎of ‎Rust ‎before ‎1.77.2 ‎on‏ ‎Windows‏ ‎are‏ ‎impacted ‎by‏ ‎this ‎vulnerability

📌Broader‏ ‎Impact: The ‎vulnerability‏ ‎also‏ ‎affects ‎other‏ ‎programming ‎languages, ‎including ‎Erlang, ‎Go,‏ ‎Haskell, ‎Java,‏ ‎Node.js,‏ ‎PHP, ‎Python, ‎and‏ ‎Ruby, ‎though‏ ‎not ‎all ‎have ‎released‏ ‎patches

📌Mitigation‏ ‎Recommendations: Users ‎are‏ ‎advised ‎to‏ ‎move ‎batch ‎files ‎to ‎a‏ ‎directory‏ ‎not ‎included‏ ‎in ‎the‏ ‎PATH ‎environment ‎variable ‎to ‎prevent‏ ‎unexpected‏ ‎execution.‏ ‎Developers ‎should‏ ‎upgrade ‎to‏ ‎Rust ‎version‏ ‎1.77.2‏ ‎to ‎patch‏ ‎the ‎vulnerability

📌Discovery ‎and ‎Reporting: ‎The‏ ‎vulnerability ‎was‏ ‎discovered‏ ‎by ‎a ‎security‏ ‎engineer ‎from‏ ‎Flatt ‎Security ‎known ‎as‏ ‎RyotaK‏ ‎and ‎reported‏ ‎to ‎the‏ ‎CERT ‎Coordination ‎Center ‎(CERT/CC)

📌Response ‎from‏ ‎Rust:‏ ‎The ‎Rust‏ ‎Security ‎Response‏ ‎Working ‎Group ‎acknowledged ‎the ‎issue‏ ‎and‏ ‎has‏ ‎since ‎improved‏ ‎the ‎robustness‏ ‎of ‎the‏ ‎escaping‏ ‎code ‎and‏ ‎modified ‎the ‎Command ‎API ‎to‏ ‎return ‎an‏ ‎InvalidInput‏ ‎error ‎if ‎an‏ ‎argument ‎cannot‏ ‎be ‎safely ‎escaped

📌Other ‎Languages'‏ ‎Response: Patches‏ ‎have ‎been‏ ‎released ‎by‏ ‎maintainers ‎of ‎Haskell, ‎Node.js, ‎PHP,‏ ‎and‏ ‎yt-dlp ‎to‏ ‎address ‎the‏ ‎command ‎injection ‎bug

Читать: 2+ мин
logo Overkill Security

Dex & Nexus

The ‎article details‏ ‎technical ‎aspects ‎of ‎dealing ‎with‏ ‎a ‎specific‏ ‎Android‏ ‎banking ‎trojan, ‎also‏ ‎broader ‎themes‏ ‎in ‎malware ‎analysis, ‎such‏ ‎as‏ ‎the ‎use‏ ‎of ‎obfuscation‏ ‎techniques ‎and ‎the ‎tools ‎available‏ ‎to‏ ‎counteract ‎these‏ ‎methods

📌String ‎Obfuscation‏ ‎Mechanism: ‎The ‎Nexus ‎banking ‎trojan‏ ‎uses‏ ‎a‏ ‎string ‎obfuscation‏ ‎mechanism ‎extensively‏ ‎throughout ‎its‏ ‎application‏ ‎code. ‎This‏ ‎complicates ‎the ‎analysis ‎and ‎understanding‏ ‎of ‎the‏ ‎application’s‏ ‎functionality.

📌Analysis ‎Tools: ‎The‏ ‎analysis ‎mentions‏ ‎the ‎use ‎of ‎both‏ ‎manual‏ ‎decoding ‎and‏ ‎paid ‎tools‏ ‎like ‎the ‎JEB ‎Decompiler ‎for‏ ‎identifying‏ ‎and ‎patching‏ ‎the ‎obfuscated‏ ‎code.

📌Dalvik ‎Bytecode ‎Inspection: The ‎case ‎study‏ ‎explores‏ ‎modifying‏ ‎the ‎obfuscated‏ ‎methods ‎by‏ ‎inspecting ‎the‏ ‎Dalvik‏ ‎bytecode, ‎which‏ ‎is ‎part ‎of ‎the ‎DEX‏ ‎files ‎in‏ ‎Android‏ ‎applications.

📌Tool ‎Release ‎—‏ ‎dexmod: a ‎tool‏ ‎called ‎dexmod, ‎developed ‎to‏ ‎assist‏ ‎in ‎the‏ ‎patching ‎of‏ ‎Dalvik ‎bytecode ‎that ‎exemplifies ‎how‏ ‎DEX‏ ‎files ‎can‏ ‎be ‎modified‏ ‎to ‎simplify ‎the ‎analysis ‎of‏ ‎Android‏ ‎applications.

📌Application‏ ‎Permissions: The ‎analysis‏ ‎of ‎the‏ ‎AndroidManifest.xml ‎file‏ ‎reveals‏ ‎that ‎the‏ ‎trojan ‎requests ‎access ‎to ‎sensitive‏ ‎information ‎such‏ ‎as‏ ‎SMS ‎messages, ‎contacts,‏ ‎and ‎phone‏ ‎calls.

📌Obfuscated ‎Methods ‎and ‎Patching:‏ ‎Specific‏ ‎methods ‎like‏ ‎bleakperfect ‎()‏ ‎are ‎highlighted ‎for ‎containing ‎dead‏ ‎code‏ ‎and ‎for‏ ‎their ‎role‏ ‎in ‎decoding ‎strings ‎using ‎XOR‏ ‎operations.‏ ‎The‏ ‎article ‎discusses‏ ‎patching ‎these‏ ‎methods ‎to‏ ‎remove‏ ‎redundant ‎code‏ ‎and ‎simplify ‎the ‎analysis.

📌DEX ‎File‏ ‎Structure: ‎The‏ ‎case‏ ‎study ‎provides ‎insights‏ ‎into ‎the‏ ‎structure ‎of ‎DEX ‎files,‏ ‎including‏ ‎sections ‎like‏ ‎headers, ‎string‏ ‎tables, ‎class ‎definitions, ‎and ‎method‏ ‎code.‏ ‎It ‎explains‏ ‎how ‎classes‏ ‎and ‎methods ‎are ‎defined ‎and‏ ‎referenced‏ ‎within‏ ‎these ‎files.

📌Checksum‏ ‎and ‎Signature‏ ‎Updates: ‎The‏ ‎necessity‏ ‎of ‎updating‏ ‎checksum ‎and ‎SHA-1 ‎signature ‎values‏ ‎in ‎the‏ ‎DEX‏ ‎file’s ‎header ‎to‏ ‎ensure ‎content‏ ‎verification ‎is ‎emphasized.

Читать: 3+ мин
logo Overkill Security

M-Trends 2024 / Google Mandiant report

The ‎Google‏ ‎Mandiant ‎report, ‎as ‎detailed ‎in‏ ‎the ‎M-Trends‏ ‎2024,‏ ‎highlights ‎a ‎significant‏ ‎reduction ‎in‏ ‎the ‎time ‎it ‎takes‏ ‎for‏ ‎organizations ‎to‏ ‎detect ‎cyber‏ ‎intrusions, ‎marking ‎a ‎notable ‎improvement‏ ‎in‏ ‎cybersecurity ‎defenses‏ ‎globally. ‎It‏ ‎provides ‎a ‎mixed ‎but ‎cautiously‏ ‎optimistic‏ ‎view‏ ‎of ‎the‏ ‎current ‎state‏ ‎of ‎cybersecurity.

Reduction‏ ‎in‏ ‎Median ‎Dwell‏ ‎Time

The ‎global ‎median ‎dwell ‎time,‏ ‎which ‎measures‏ ‎the‏ ‎average ‎duration ‎attackers‏ ‎remain ‎undetected‏ ‎within ‎a ‎network, ‎has‏ ‎decreased‏ ‎to ‎its‏ ‎lowest ‎point‏ ‎in ‎over ‎a ‎decade. ‎In‏ ‎2023,‏ ‎this ‎figure‏ ‎was ‎recorded‏ ‎at ‎10 ‎days, ‎down ‎from‏ ‎16‏ ‎days‏ ‎in ‎2022,‏ ‎and ‎significantly‏ ‎lower ‎than‏ ‎the‏ ‎78 ‎days‏ ‎observed ‎six ‎years ‎ago

Increase ‎in‏ ‎Ransomware ‎Detection

The‏ ‎report‏ ‎attributes ‎part ‎of‏ ‎the ‎reduction‏ ‎in ‎dwell ‎time ‎to‏ ‎an‏ ‎increase ‎in‏ ‎ransomware ‎incidents,‏ ‎which ‎are ‎typically ‎easier ‎to‏ ‎detect‏ ‎due ‎to‏ ‎their ‎disruptive‏ ‎nature. ‎Ransomware-related ‎intrusions ‎accounted ‎for‏ ‎23%‏ ‎of‏ ‎the ‎total‏ ‎in ‎2023,‏ ‎up ‎from‏ ‎18%‏ ‎in ‎2022.‏ ‎These ‎incidents ‎are ‎generally ‎identified‏ ‎more ‎quickly,‏ ‎with‏ ‎ransomware ‎being ‎detected‏ ‎in ‎about‏ ‎six ‎days ‎when ‎the‏ ‎notification‏ ‎comes ‎from‏ ‎an ‎internal‏ ‎source, ‎and ‎in ‎five ‎days‏ ‎from‏ ‎external ‎notifications

Improvement‏ ‎in ‎Internal‏ ‎Detection ‎Capabilities

There ‎has ‎been ‎a‏ ‎notable‏ ‎improvement‏ ‎in ‎the‏ ‎ability ‎of‏ ‎organizations ‎to‏ ‎detect‏ ‎compromises ‎internally.‏ ‎In ‎2023, ‎46% ‎of ‎intrusions‏ ‎were ‎detected‏ ‎internally,‏ ‎up ‎from ‎37%‏ ‎in ‎2022.‏ ‎This ‎suggests ‎that ‎investments‏ ‎in‏ ‎cybersecurity ‎tools‏ ‎and ‎training‏ ‎are ‎yielding ‎positive ‎results.

Geographic ‎and‏ ‎Sectoral‏ ‎Variations

📌While ‎the‏ ‎global ‎trend‏ ‎shows ‎improvement, ‎not ‎all ‎regions‏ ‎experienced‏ ‎the‏ ‎same ‎level‏ ‎of ‎progress.‏ ‎For ‎instance,‏ ‎organizations‏ ‎in ‎the‏ ‎Asia-Pacific ‎region ‎saw ‎a ‎dramatic‏ ‎decrease ‎in‏ ‎median‏ ‎dwell ‎time ‎to‏ ‎nine ‎days,‏ ‎whereas ‎in ‎Europe, ‎the‏ ‎Middle‏ ‎East, ‎and‏ ‎Africa, ‎the‏ ‎median ‎dwell ‎time ‎slightly ‎increased

📌Financial‏ ‎services,‏ ‎business ‎and‏ ‎professional ‎services,‏ ‎high ‎technology, ‎retail ‎and ‎hospitality,‏ ‎and‏ ‎health‏ ‎sectors ‎were‏ ‎identified ‎as‏ ‎the ‎most‏ ‎targeted‏ ‎by ‎cyber‏ ‎attackers, ‎primarily ‎due ‎to ‎the‏ ‎sensitive ‎nature‏ ‎of‏ ‎the ‎data ‎they‏ ‎handle

Evolving ‎Threat‏ ‎Tactics

📌The ‎report ‎also ‎highlights‏ ‎a‏ ‎shift ‎in‏ ‎attacker ‎tactics,‏ ‎with ‎an ‎increased ‎focus ‎on‏ ‎evasion‏ ‎techniques. ‎Cyber‏ ‎attackers ‎are‏ ‎increasingly ‎targeting ‎edge ‎devices ‎and‏ ‎exploiting‏ ‎zero-day‏ ‎vulnerabilities ‎to‏ ‎maintain ‎their‏ ‎presence ‎undetected‏ ‎within‏ ‎networks ‎for‏ ‎extended ‎periods

📌Espionage ‎activities, ‎particularly ‎by‏ ‎groups ‎allegedly‏ ‎linked‏ ‎to ‎China, ‎have‏ ‎intensified, ‎with‏ ‎these ‎groups ‎focusing ‎on‏ ‎acquiring‏ ‎zero-day ‎exploits‏ ‎and ‎targeting‏ ‎platforms ‎with ‎minimal ‎security ‎measures

Challenges‏ ‎and‏ ‎Recommendations

📌Despite ‎the‏ ‎improvements, ‎the‏ ‎report ‎underscores ‎the ‎ongoing ‎challenges‏ ‎in‏ ‎cybersecurity.‏ ‎Attackers ‎are‏ ‎adapting ‎quickly,‏ ‎utilizing ‎sophisticated‏ ‎methods‏ ‎such ‎as‏ ‎«living ‎off ‎the ‎land» ‎tactics‏ ‎and ‎zero-day‏ ‎exploits

📌Mandiant‏ ‎emphasizes ‎the ‎importance‏ ‎of ‎robust‏ ‎security ‎strategies ‎that ‎include‏ ‎effective‏ ‎threat ‎hunting‏ ‎programs ‎and‏ ‎comprehensive ‎investigations ‎and ‎remediations ‎following‏ ‎breaches

Читать: 1+ мин
logo Overkill Security

BiTE project

The ‎BiTE‏ ‎project ‎on ‎GitHub is ‎a ‎disassembler‏ ‎focused ‎on‏ ‎comprehensive‏ ‎Rust ‎support.

Purpose

BiTE ‎is‏ ‎designed ‎as‏ ‎a ‎platform-agnostic ‎executable ‎analysis‏ ‎tool.‏ ‎Its ‎primary‏ ‎purpose ‎is‏ ‎to ‎provide ‎an ‎environment ‎for‏ ‎inspecting‏ ‎the ‎content‏ ‎of ‎binaries‏ ‎and ‎their ‎debug ‎information. ‎The‏ ‎tool‏ ‎aims‏ ‎to ‎support‏ ‎various ‎architectures,‏ ‎making ‎it‏ ‎versatile‏ ‎for ‎different‏ ‎executable ‎formats.

Features

📌 Assembly ‎Listing ‎Viewing: Allows ‎users‏ ‎to ‎view‏ ‎a‏ ‎binary’s ‎disassembly ‎alongside‏ ‎its ‎associated‏ ‎source ‎code.

📌 GUI ‎Porting: Plans ‎to‏ ‎port‏ ‎the ‎graphical‏ ‎user ‎interface‏ ‎to ‎wgpu ‎+ ‎winit.

📌 Interactive ‎Elements: Includes‏ ‎a‏ ‎header ‎with‏ ‎buttons ‎and‏ ‎options, ‎assembly ‎listing ‎exploration, ‎and‏ ‎an‏ ‎interactive‏ ‎terminal.

📌 Assembly ‎Instruction‏ ‎Byte ‎Patching: Enables‏ ‎users ‎to‏ ‎modify‏ ‎the ‎binary‏ ‎directly.

📌 Hex ‎Binary ‎Viewer: Provides ‎a ‎hexadecimal‏ ‎view ‎of‏ ‎the‏ ‎binary ‎for ‎detailed‏ ‎inspection.

📌 Debugging ‎Front-Ends: Supports‏ ‎front-end ‎interfaces ‎for ‎debugging‏ ‎purposes.

📌 Architecture‏ ‎Support: Includes ‎support‏ ‎for ‎multiple‏ ‎architectures ‎such ‎as ‎X86-64, ‎AArch64/Armv7,‏ ‎Riscv64gc/Riscv32gc,‏ ‎and ‎MIPS-V.

📌 Demangling‏ ‎Support: Offers ‎demangling‏ ‎for ‎various ‎targets ‎including ‎MSVC,‏ ‎Itanium,‏ ‎and‏ ‎Rust.

📌 Decoding ‎Data‏ ‎Structures: Capable ‎of‏ ‎decoding ‎data‏ ‎structures‏ ‎based ‎on‏ ‎each ‎section ‎of ‎the ‎binary.

📌 Assembly‏ ‎Listing ‎Lifting: Transforms‏ ‎assembly‏ ‎listings ‎into ‎a‏ ‎higher-level ‎representation.

📌 Resolving‏ ‎Addresses: Helps ‎in ‎resolving ‎addresses‏ ‎within‏ ‎the ‎binary.

📌 Interpreting‏ ‎Non-Code ‎Data: Allows‏ ‎for ‎the ‎interpretation ‎of ‎data‏ ‎within‏ ‎the ‎binary‏ ‎that ‎is‏ ‎not ‎executable ‎code.

📌 Creating ‎Labels ‎for‏ ‎Relative‏ ‎Jumps: Facilitates‏ ‎the ‎creation‏ ‎of ‎labels‏ ‎for ‎relative‏ ‎jump‏ ‎instructions ‎within‏ ‎the ‎disassembly.

Читать: 1+ мин
logo Overkill Security

AttackGen

The ‎GitHub‏ ‎repository ‎for ‎AttackGen provides ‎a ‎cybersecurity‏ ‎incident ‎response‏ ‎testing‏ ‎tool ‎that ‎integrates‏ ‎large ‎language‏ ‎models ‎with ‎the ‎MITRE‏ ‎ATT&‏ ‎CK ‎framework‏ ‎to ‎generate‏ ‎tailored ‎incident ‎response ‎scenarios

Features

📌 Scenario ‎Generation: AttackGen‏ ‎can‏ ‎generate ‎unique‏ ‎incident ‎response‏ ‎scenarios ‎based ‎on ‎selected ‎threat‏ ‎actor‏ ‎groups

📌 Customization: Users‏ ‎can ‎specify‏ ‎their ‎organization’s‏ ‎size ‎and‏ ‎industry‏ ‎for ‎scenarios‏ ‎tailored ‎to ‎their ‎specific ‎context

📌 MITRE‏ ‎ATT& ‎CK‏ ‎Integration: The‏ ‎tool ‎displays ‎a‏ ‎detailed ‎list‏ ‎of ‎techniques ‎used ‎by‏ ‎the‏ ‎chosen ‎threat‏ ‎actor ‎group‏ ‎according ‎to ‎the ‎MITRE ‎ATT&‏ ‎CK‏ ‎framework

📌 Custom ‎Scenarios: There‏ ‎is ‎an‏ ‎option ‎to ‎create ‎custom ‎scenarios‏ ‎based‏ ‎on‏ ‎a ‎selection‏ ‎of ‎ATT&‏ ‎CK ‎techniques

📌 Feedback‏ ‎Capture: AttackGen‏ ‎includes ‎a‏ ‎feature ‎to ‎capture ‎user ‎feedback‏ ‎on ‎the‏ ‎quality‏ ‎of ‎the ‎generated‏ ‎scenarios

📌 Docker ‎Container: The‏ ‎tool ‎is ‎available ‎as‏ ‎a‏ ‎Docker ‎container‏ ‎image ‎for‏ ‎easy ‎deployment

Usage

📌 Running ‎the ‎Tool: Instructions ‎are‏ ‎provided‏ ‎for ‎running‏ ‎AttackGen ‎and‏ ‎navigating ‎to ‎the ‎provided ‎URL‏ ‎in‏ ‎a‏ ‎web ‎browser

📌 Scenario‏ ‎Selection: Users ‎can‏ ‎select ‎their‏ ‎company’s‏ ‎industry, ‎size,‏ ‎and ‎the ‎desired ‎threat ‎actor‏ ‎group ‎to‏ ‎generate‏ ‎scenarios

Requirements

📌 Python: A ‎recent ‎version‏ ‎of ‎Python‏ ‎is ‎required

📌 Python ‎Packages: Dependencies ‎include‏ ‎pandas,‏ ‎streamlit, ‎and‏ ‎other ‎packages‏ ‎necessary ‎for ‎the ‎custom ‎libraries‏ ‎(langchain‏ ‎and ‎mitreattack)

📌 API‏ ‎Keys: An ‎OpenAI‏ ‎API ‎key ‎is ‎needed, ‎and‏ ‎a‏ ‎LangChain‏ ‎API ‎key‏ ‎is ‎optional

Читать: 1+ мин
logo Overkill Security

What2Log

The ‎What2Log is‏ ‎a ‎blog ‎dedicated ‎to ‎discussing‏ ‎various ‎aspects‏ ‎of‏ ‎log ‎management ‎and‏ ‎analysis. ‎The‏ ‎blog ‎features ‎updates ‎on‏ ‎the‏ ‎What2Log ‎tool,‏ ‎insights ‎into‏ ‎specific ‎logging ‎features, ‎and ‎discussions‏ ‎on‏ ‎challenges ‎related‏ ‎to ‎log‏ ‎management. ‎Key ‎topics ‎covered ‎in‏ ‎the‏ ‎blog‏ ‎include:

📌What2Log ‎Updates: The‏ ‎blog ‎provides‏ ‎detailed ‎updates‏ ‎on‏ ‎new ‎versions‏ ‎of ‎the ‎What2Log ‎tool, ‎such‏ ‎as ‎the‏ ‎Aspen‏ ‎and ‎Alder ‎updates.‏ ‎These ‎posts‏ ‎discuss ‎the ‎changes ‎and‏ ‎enhancements‏ ‎introduced ‎in‏ ‎these ‎versions.

📌EventRecordID: One‏ ‎of ‎the ‎blog ‎posts ‎highlights‏ ‎the‏ ‎EventRecordID, ‎a‏ ‎hidden ‎XML‏ ‎tag ‎in ‎Windows ‎Event ‎Logs‏ ‎that‏ ‎enriches‏ ‎log ‎information.

📌Event‏ ‎ID ‎4672: This‏ ‎post ‎discusses‏ ‎the‏ ‎significance ‎of‏ ‎Event ‎ID ‎4672 ‎in ‎Windows,‏ ‎which ‎logs‏ ‎special‏ ‎privileges ‎assigned ‎to‏ ‎new ‎logons.

📌Log‏ ‎Management ‎Challenges: Several ‎posts ‎in‏ ‎the‏ ‎blog ‎series‏ ‎titled ‎«The‏ ‎Struggle ‎is ‎Real» ‎address ‎various‏ ‎challenges‏ ‎in ‎log‏ ‎management, ‎including‏ ‎log ‎volume ‎management, ‎log ‎analysis,‏ ‎event‏ ‎correlation,‏ ‎and ‎log‏ ‎aggregation. ‎These‏ ‎posts ‎discuss‏ ‎the‏ ‎complexities ‎and‏ ‎necessary ‎considerations ‎in ‎effectively ‎managing‏ ‎and ‎analyzing‏ ‎logs.

Overall,‏ ‎the ‎blog ‎serves‏ ‎as ‎a‏ ‎resource ‎for ‎individuals ‎interested‏ ‎in‏ ‎the ‎technical‏ ‎aspects ‎of‏ ‎log ‎management, ‎offering ‎both ‎educational‏ ‎content‏ ‎and ‎updates‏ ‎on ‎the‏ ‎What2Log ‎tool ‎on ‎Github as ‎well

Читать: 2+ мин
logo Overkill Security

Meta Pixel tracker script

Cybersecurity ‎researchers‏ ‎have ‎recently ‎uncovered ‎a ‎sophisticated‏ ‎credit ‎card‏ ‎skimming‏ ‎operation ‎that ‎cleverly‏ ‎masquerades ‎as‏ ‎a ‎harmless ‎Facebook ‎tracker,‏ ‎specifically‏ ‎a ‎fake‏ ‎Meta ‎Pixel‏ ‎tracker ‎script.

The ‎Mechanism ‎of ‎the‏ ‎Attack

The‏ ‎attackers ‎exploit‏ ‎the ‎trust‏ ‎placed ‎in ‎widely ‎recognized ‎scripts,‏ ‎such‏ ‎as‏ ‎Google ‎Analytics‏ ‎or ‎JQuery,‏ ‎by ‎naming‏ ‎their‏ ‎malicious ‎scripts‏ ‎in ‎a ‎manner ‎that ‎mimics‏ ‎these ‎legitimate‏ ‎services.‏ ‎The ‎fake ‎Meta‏ ‎Pixel ‎tracker‏ ‎script, ‎upon ‎closer ‎inspection,‏ ‎reveals‏ ‎JavaScript ‎code‏ ‎that ‎substitutes‏ ‎references ‎to ‎the ‎legitimate ‎domain‏ ‎«connect.facebook[.]net»‏ ‎with ‎«b-connected[.]com,»‏ ‎a ‎legitimate‏ ‎e-commerce ‎website ‎that ‎has ‎been‏ ‎compromised‏ ‎to‏ ‎host ‎the‏ ‎skimmer ‎code.‏ ‎This ‎substitution‏ ‎is‏ ‎a ‎key‏ ‎part ‎of ‎the ‎skimmer’s ‎operation,‏ ‎as ‎it‏ ‎allows‏ ‎the ‎malicious ‎code‏ ‎to ‎execute‏ ‎under ‎the ‎guise ‎of‏ ‎a‏ ‎legitimate ‎service

The‏ ‎Skimming ‎Process

Once‏ ‎the ‎malicious ‎script ‎is ‎loaded‏ ‎on‏ ‎a ‎compromised‏ ‎website, ‎it‏ ‎monitors ‎for ‎specific ‎actions, ‎such‏ ‎as‏ ‎a‏ ‎visitor ‎reaching‏ ‎a ‎checkout‏ ‎page. ‎At‏ ‎this‏ ‎point, ‎it‏ ‎serves ‎a ‎fraudulent ‎overlay ‎designed‏ ‎to ‎capture‏ ‎the‏ ‎credit ‎card ‎details‏ ‎entered ‎by‏ ‎the ‎victim. ‎The ‎stolen‏ ‎information‏ ‎is ‎then‏ ‎exfiltrated ‎to‏ ‎another ‎compromised ‎site, ‎«http://www.donjuguetes[.]es,» ‎showcasing‏ ‎the‏ ‎multi-layered ‎nature‏ ‎of ‎this‏ ‎attack

Broader ‎Implications

This ‎incident ‎underscores ‎the‏ ‎importance‏ ‎of‏ ‎vigilance ‎and‏ ‎robust ‎security‏ ‎practices ‎for‏ ‎website‏ ‎owners, ‎especially‏ ‎those ‎operating ‎e-commerce ‎platforms. ‎The‏ ‎use ‎of‏ ‎fake‏ ‎scripts ‎that ‎mimic‏ ‎legitimate ‎services‏ ‎is ‎a ‎cunning ‎strategy‏ ‎that‏ ‎can ‎easily‏ ‎deceive ‎even‏ ‎the ‎most ‎cautious ‎individuals. ‎As‏ ‎such,‏ ‎it ‎is‏ ‎essential ‎to‏ ‎employ ‎comprehensive ‎security ‎measures, ‎including‏ ‎the‏ ‎use‏ ‎of ‎intrusion‏ ‎detection ‎systems‏ ‎and ‎website‏ ‎monitoring,‏ ‎to ‎detect‏ ‎and ‎mitigate ‎such ‎threats

Читать: 1+ мин
logo Overkill Security

EDR features' comparison

This ‎project aims‏ ‎to ‎track ‎and ‎compare ‎the‏ ‎telemetry ‎features‏ ‎implemented‏ ‎in ‎various ‎EDR‏ ‎systems ‎for‏ ‎Windows. ‎The ‎document ‎serves‏ ‎as‏ ‎a ‎telemetry‏ ‎comparison ‎table,‏ ‎detailing ‎the ‎capabilities ‎of ‎different‏ ‎EDR‏ ‎products ‎in‏ ‎capturing ‎specific‏ ‎types ‎of ‎telemetry ‎data ‎that‏ ‎are‏ ‎relevant‏ ‎to ‎cybersecurity.

📌CrowdStrike‏ ‎and ‎Microsoft‏ ‎Defender ‎for‏ ‎Endpoint‏ ‎(MDE) ‎appear‏ ‎to ‎have ‎a ‎comprehensive ‎implementation‏ ‎of ‎features‏ ‎across‏ ‎multiple ‎categories. ‎Both‏ ‎products ‎have‏ ‎a ‎high ‎number ‎of‏ ‎features‏ ‎marked ‎as‏ ‎fully ‎implemented‏ ‎(✅) ‎across ‎various ‎telemetry ‎feature‏ ‎categories.‏ ‎This ‎indicates‏ ‎a ‎broad‏ ‎coverage ‎in ‎terms ‎of ‎telemetry‏ ‎data‏ ‎collection‏ ‎capabilities, ‎which‏ ‎is ‎crucial‏ ‎for ‎effective‏ ‎endpoint‏ ‎detection ‎and‏ ‎response.

📌On ‎the ‎other ‎end ‎of‏ ‎the ‎spectrum,‏ ‎WatchGuard‏ ‎and ‎Harfanglab ‎have‏ ‎a ‎noticeable‏ ‎number ‎of ‎features ‎marked‏ ‎as‏ ‎not ‎implemented‏ ‎(❌) ‎or‏ ‎partially ‎implemented ‎(⚠️). ‎This ‎suggests‏ ‎that‏ ‎these ‎products‏ ‎may ‎have‏ ‎gaps ‎in ‎their ‎telemetry ‎data‏ ‎collection‏ ‎capabilities‏ ‎compared ‎to‏ ‎other ‎EDR‏ ‎products ‎listed‏ ‎in‏ ‎the ‎document.

Читать: 2+ мин
logo Overkill Security

Stories of data leakage

There ‎are‏ ‎several ‎mentioned ‎involve ‎serious ‎breaches‏ ‎of ‎trust‏ ‎and‏ ‎security ‎within ‎the‏ ‎U.S. ‎military,‏ ‎highlighting ‎the ‎challenges ‎of‏ ‎safeguarding‏ ‎sensitive ‎information‏ ‎and ‎technology.

📌 U.S.‏ ‎Navy ‎contractor ‎who, ‎in ‎2007,‏ ‎inserted‏ ‎malicious ‎code‏ ‎into ‎the‏ ‎software ‎of ‎a ‎submarine’s ‎threat‏ ‎detection‏ ‎system.‏ ‎This ‎act‏ ‎was ‎a‏ ‎deliberate ‎sabotage‏ ‎that‏ ‎could ‎have‏ ‎compromised ‎the ‎safety ‎and ‎operational‏ ‎capabilities ‎of‏ ‎the‏ ‎submarine. ‎Malicious ‎code‏ ‎in ‎such‏ ‎critical ‎systems ‎could ‎potentially‏ ‎disable‏ ‎threat ‎detection,‏ ‎leading ‎to‏ ‎undetected ‎navigation ‎hazards ‎or ‎enemy‏ ‎actions.

📌Robert‏ ‎Birchum, ‎a‏ ‎retired ‎U.S.‏ ‎Air ‎Force ‎intelligence ‎officer, ‎who‏ ‎was‏ ‎sentenced‏ ‎to ‎three‏ ‎years ‎in‏ ‎federal ‎prison‏ ‎for‏ ‎unlawfully ‎possessing‏ ‎and ‎retaining ‎classified ‎documents. ‎Birchum,‏ ‎who ‎retired‏ ‎in‏ ‎2018 ‎as ‎a‏ ‎lieutenant ‎colonel,‏ ‎had ‎a ‎29-year ‎career‏ ‎during‏ ‎which ‎he‏ ‎served ‎in‏ ‎various ‎intelligence ‎positions, ‎including ‎roles‏ ‎that‏ ‎required ‎him‏ ‎to ‎work‏ ‎with ‎classified ‎intelligence ‎information ‎for‏ ‎the‏ ‎Joint‏ ‎Special ‎Operations‏ ‎Command, ‎the‏ ‎Special ‎Operations‏ ‎Command,‏ ‎and ‎the‏ ‎Office ‎of ‎the ‎Director ‎of‏ ‎National ‎Intelligence.

📌Harold‏ ‎Martin,‏ ‎a ‎former ‎National‏ ‎Security ‎Agency‏ ‎contractor, ‎was ‎arrested ‎in‏ ‎August‏ ‎2016 ‎for‏ ‎stealing ‎and‏ ‎retaining ‎highly ‎classified ‎top-secret ‎documents‏ ‎covering‏ ‎20 ‎years.‏ ‎Martin ‎kept‏ ‎these ‎documents ‎in ‎his ‎home‏ ‎and‏ ‎vehicle.‏ ‎The ‎stolen‏ ‎documents ‎contained‏ ‎sensitive ‎information‏ ‎about‏ ‎NSA ‎planning,‏ ‎intelligence ‎collection, ‎U.S. ‎Cyber ‎Command‏ ‎capabilities, ‎and‏ ‎gaps‏ ‎in ‎U.S. ‎cyber‏ ‎capabilities.

📌Jerry ‎Chun‏ ‎Shing ‎Lee, ‎a ‎former‏ ‎CIA‏ ‎officer, ‎was‏ ‎arrested ‎in‏ ‎January ‎2018 ‎on ‎charges ‎of‏ ‎unlawful‏ ‎retention ‎of‏ ‎national ‎defense‏ ‎information. ‎Lee ‎possessed ‎notebooks ‎that‏ ‎contained‏ ‎handwritten‏ ‎notes ‎of‏ ‎classified ‎information,‏ ‎including ‎the‏ ‎true‏ ‎names ‎and‏ ‎phone ‎numbers ‎of ‎assets ‎and‏ ‎covert ‎CIA‏ ‎operational‏ ‎notes.

📌Jack ‎Teixeira, ‎a‏ ‎member ‎of‏ ‎the ‎Massachusetts ‎Air ‎National‏ ‎Guard,‏ ‎pleaded ‎guilty‏ ‎to ‎leaking‏ ‎highly ‎classified ‎military ‎documents ‎on‏ ‎a‏ ‎social ‎media‏ ‎platform. ‎Teixeira‏ ‎faced ‎a ‎sentence ‎of ‎11‏ ‎to‏ ‎16‏ ‎years ‎in‏ ‎prison ‎for‏ ‎his ‎actions.

Читать: 3+ мин
logo Overkill Security

Evilginx + GoPhish

The ‎article‏ ‎from ‎BreakDev discusses ‎the ‎integration ‎of‏ ‎Evilginx ‎3.3‏ ‎with‏ ‎GoPhish, ‎a ‎significant‏ ‎update ‎that‏ ‎enhances ‎phishing ‎campaign ‎capabilities.‏ ‎These‏ ‎updates ‎to‏ ‎Evilginx ‎and‏ ‎its ‎integration ‎with ‎GoPhish ‎represent‏ ‎significant‏ ‎advancements ‎in‏ ‎phishing ‎campaign‏ ‎technology, ‎offering ‎users ‎more ‎sophisticated‏ ‎tools‏ ‎for‏ ‎creating ‎and‏ ‎managing ‎phishing‏ ‎attempts ‎with‏ ‎enhanced‏ ‎customization ‎and‏ ‎tracking ‎capabilities.

Here ‎are ‎the ‎key‏ ‎points ‎and‏ ‎new‏ ‎features ‎introduced:

📌Integration ‎with‏ ‎GoPhish: Evilginx ‎now‏ ‎officially ‎integrates ‎with ‎GoPhish‏ ‎by‏ ‎Jordan ‎Wright.‏ ‎This ‎collaboration‏ ‎allows ‎users ‎to ‎create ‎phishing‏ ‎campaigns‏ ‎that ‎send‏ ‎emails ‎with‏ ‎valid ‎Evilginx ‎lure ‎URLs, ‎leveraging‏ ‎GoPhish’s‏ ‎user‏ ‎interface ‎to‏ ‎monitor ‎the‏ ‎campaign’s ‎effectiveness,‏ ‎including‏ ‎email ‎opens,‏ ‎lure ‎URL ‎clicks, ‎and ‎successful‏ ‎session ‎captures.

📌API‏ ‎Enhancements: The‏ ‎update ‎has ‎introduced‏ ‎additional ‎API‏ ‎endpoints ‎in ‎GoPhish, ‎enabling‏ ‎changes‏ ‎to ‎the‏ ‎results ‎status‏ ‎for ‎every ‎sent ‎email. ‎This‏ ‎improvement‏ ‎facilitates ‎more‏ ‎dynamic ‎and‏ ‎responsive ‎campaign ‎management.

📌Lure ‎URL ‎Generation: In‏ ‎the‏ ‎new‏ ‎workflow, ‎when‏ ‎creating ‎a‏ ‎campaign ‎in‏ ‎GoPhish,‏ ‎users ‎no‏ ‎longer ‎select ‎a ‎«Landing ‎Page.»‏ ‎Instead, ‎they‏ ‎generate‏ ‎a ‎lure ‎URL‏ ‎in ‎Evilginx‏ ‎and ‎input ‎it ‎into‏ ‎the‏ ‎«Evilginx ‎Lure‏ ‎URL» ‎text‏ ‎box. ‎This ‎process ‎streamlines ‎the‏ ‎creation‏ ‎of ‎phishing‏ ‎campaigns.

📌Custom ‎Parameters‏ ‎and ‎Personalization: GoPhish ‎automatically ‎generates ‎encrypted‏ ‎custom‏ ‎parameters‏ ‎with ‎personalized‏ ‎content ‎for‏ ‎each ‎link‏ ‎embedded‏ ‎in ‎the‏ ‎generated ‎email ‎messages. ‎These ‎parameters‏ ‎include ‎the‏ ‎recipient’s‏ ‎first ‎name, ‎last‏ ‎name, ‎and‏ ‎email. ‎This ‎feature ‎allows‏ ‎for‏ ‎the ‎customization‏ ‎of ‎phishing‏ ‎pages ‎through ‎js_inject ‎scripts, ‎enhancing‏ ‎the‏ ‎effectiveness ‎of‏ ‎phishing ‎attempts.

📌Expanded‏ ‎TLD ‎Support: Evilginx ‎has ‎expanded ‎its‏ ‎support‏ ‎for‏ ‎new ‎Top-Level‏ ‎Domains ‎(TLDs)‏ ‎to ‎improve‏ ‎the‏ ‎efficiency ‎of‏ ‎URL ‎detection ‎in ‎proxied ‎packets.‏ ‎This ‎update‏ ‎aims‏ ‎to ‎better ‎differentiate‏ ‎between ‎phishing‏ ‎and ‎original ‎domains ‎by‏ ‎recognizing‏ ‎URLs ‎ending‏ ‎with ‎a‏ ‎broader ‎range ‎of ‎known ‎TLDs.‏ ‎The‏ ‎updated ‎list‏ ‎includes ‎a‏ ‎variety ‎of ‎TLDs, ‎such ‎as‏ ‎.aero,‏ ‎.arpa,‏ ‎.biz, ‎.cloud,‏ ‎.gov, ‎.info,‏ ‎.net, ‎.org,‏ ‎and‏ ‎many ‎others,‏ ‎including ‎all ‎known ‎2-character ‎TLDs.

**

Evilginx‏ ‎and ‎GoPhish‏ ‎are‏ ‎tools ‎used ‎in‏ ‎cybersecurity, ‎particularly‏ ‎in ‎the ‎context ‎of‏ ‎phishing‏ ‎simulations ‎and‏ ‎man-in-the-middle ‎(MitM)‏ ‎attack ‎frameworks. ‎They ‎serve ‎different‏ ‎purposes‏ ‎but ‎can‏ ‎be ‎used‏ ‎together ‎to ‎enhance ‎phishing ‎campaigns‏ ‎and‏ ‎security‏ ‎testing.

📌Evilginx ‎is‏ ‎a ‎man-in-the-middle‏ ‎attack ‎framework‏ ‎that‏ ‎can ‎bypass‏ ‎two-factor ‎authentication ‎(2FA) ‎mechanisms.

  • It ‎works‏ ‎by ‎tricking‏ ‎a‏ ‎user ‎into ‎visiting‏ ‎a ‎proxy‏ ‎site ‎that ‎looks ‎like‏ ‎the‏ ‎legitimate ‎site‏ ‎they ‎intend‏ ‎to ‎visit. ‎As ‎the ‎user‏ ‎logs‏ ‎in ‎and‏ ‎completes ‎the‏ ‎2FA ‎challenge, ‎Evilginx ‎captures ‎the‏ ‎user’s‏ ‎login‏ ‎information ‎and‏ ‎the ‎authentication‏ ‎token.
  • This ‎method‏ ‎allows‏ ‎the ‎attacker‏ ‎to ‎replay ‎the ‎token ‎and‏ ‎access ‎the‏ ‎targeted‏ ‎service ‎as ‎the‏ ‎user, ‎effectively‏ ‎bypassing ‎2FA ‎protections.

📌GoPhish ‎is‏ ‎an‏ ‎open-source ‎phishing‏ ‎toolkit ‎designed‏ ‎for ‎businesses ‎and ‎security ‎professionals‏ ‎to‏ ‎conduct ‎security‏ ‎awareness ‎training‏ ‎and ‎phishing ‎simulation ‎exercises.

  • It ‎allows‏ ‎users‏ ‎to‏ ‎create ‎and‏ ‎track ‎the‏ ‎effectiveness ‎of‏ ‎phishing‏ ‎campaigns, ‎including‏ ‎email ‎opens, ‎link ‎clicks, ‎and‏ ‎data ‎submission‏ ‎on‏ ‎phishing ‎pages.
Читать: 1+ мин
logo Overkill Security

Firebase

Firebase ‎is‏ ‎a ‎platform ‎that ‎requires ‎developers‏ ‎to ‎secure‏ ‎individual‏ ‎tables ‎and ‎rows.‏ ‎However, ‎it‏ ‎appears ‎that ‎developers ‎either‏ ‎lacked‏ ‎the ‎necessary‏ ‎security ‎training‏ ‎or ‎did ‎not ‎allocate ‎sufficient‏ ‎time‏ ‎in ‎the‏ ‎development ‎lifecycle‏ ‎to ‎apply ‎the ‎correct ‎security‏ ‎controls

Causes‏ ‎of‏ ‎the ‎Firebase‏ ‎Misconfigurations

The ‎misconfigurations‏ ‎of ‎Firebase‏ ‎instances‏ ‎that ‎led‏ ‎to ‎the ‎exposure ‎of ‎19‏ ‎million ‎plaintext‏ ‎passwords‏ ‎and ‎sensitive ‎user‏ ‎data ‎were‏ ‎primarily ‎due ‎to ‎two‏ ‎factors:

📌Lack‏ ‎of ‎Security‏ ‎Rules: Some ‎Firebase‏ ‎instances ‎had ‎no ‎security ‎rules‏ ‎enabled,‏ ‎which ‎should‏ ‎act ‎as‏ ‎a ‎first ‎line ‎of ‎defense‏ ‎against‏ ‎unauthorized‏ ‎access.

📌Incorrect ‎Setup: In‏ ‎other ‎cases,‏ ‎security ‎rules‏ ‎were‏ ‎set ‎up‏ ‎incorrectly. ‎This ‎improper ‎configuration ‎allowed‏ ‎for ‎the‏ ‎public‏ ‎exposure ‎of ‎data‏ ‎that ‎should‏ ‎have ‎been ‎private.

Affected ‎Industries

The‏ ‎misconfigured‏ ‎Firebase ‎instances‏ ‎affected ‎a‏ ‎broad ‎range ‎of ‎industries, ‎including:

📌Retail‏ ‎and‏ ‎Hospitality: Fast ‎food‏ ‎chains ‎and‏ ‎other ‎retail ‎businesses ‎were ‎among‏ ‎those‏ ‎affected,‏ ‎with ‎instances‏ ‎such ‎as‏ ‎Chattr’s ‎Firebase‏ ‎implementation‏ ‎exposing ‎user‏ ‎data.

📌Healthcare: Healthcare ‎applications ‎were ‎found ‎to‏ ‎have ‎exposed‏ ‎personal‏ ‎family ‎photos ‎and‏ ‎token ‎IDs.

📌E-commerce: E-commerce‏ ‎platforms ‎leaked ‎data ‎from‏ ‎cryptocurrency‏ ‎exchange ‎platforms.

Education:‏ ‎A ‎learning‏ ‎management ‎system ‎for ‎teachers ‎and‏ ‎students‏ ‎exposed ‎records‏ ‎of ‎27‏ ‎million ‎users.

📌Technology ‎and ‎App ‎Development: The‏ ‎very‏ ‎nature‏ ‎of ‎Firebase‏ ‎as ‎a‏ ‎development ‎platform‏ ‎means‏ ‎that ‎a‏ ‎wide ‎array ‎of ‎mobile ‎and‏ ‎web ‎applications‏ ‎across‏ ‎various ‎sectors ‎were‏ ‎impacted.

Читать: 5+ мин
logo Overkill Security

SharpTerminator

The ‎Terminator‏ ‎tool, ‎along ‎with ‎its ‎variants‏ ‎such ‎as‏ ‎SharpTerminator‏ ‎and ‎Ternimator, ‎is‏ ‎part ‎of‏ ‎a ‎class ‎of ‎attack‏ ‎known‏ ‎as ‎Bring‏ ‎Your ‎Own‏ ‎Vulnerable ‎Driver ‎(BYOVD). ‎This ‎strategy‏ ‎involves‏ ‎leveraging ‎legitimate‏ ‎but ‎vulnerable‏ ‎drivers ‎to ‎bypass ‎security ‎measures,‏ ‎terminate‏ ‎antivirus‏ ‎and ‎EDR‏ ‎processes, ‎and‏ ‎execute ‎malicious‏ ‎activities‏ ‎without ‎detection.

The‏ ‎Persistent ‎Threat ‎of ‎the ‎Terminator‏ ‎Tool

The ‎Terminator‏ ‎tool‏ ‎represents ‎a ‎significant‏ ‎threat ‎due‏ ‎to ‎its ‎ability ‎to‏ ‎disable‏ ‎security ‎solutions,‏ ‎thereby ‎facilitating‏ ‎a ‎range ‎of ‎malicious ‎activities.‏ ‎These‏ ‎activities ‎can‏ ‎range ‎from‏ ‎deploying ‎additional ‎malware ‎to ‎extensive‏ ‎system‏ ‎compromise‏ ‎and ‎operational‏ ‎disruption. ‎The‏ ‎tool ‎leverages‏ ‎the‏ ‎Bring ‎Your‏ ‎Own ‎Vulnerable ‎Driver ‎(BYOVD) ‎technique,‏ ‎exploiting ‎vulnerabilities‏ ‎in‏ ‎legitimate ‎drivers ‎to‏ ‎bypass ‎security‏ ‎measures

Technical ‎Sophistication ‎and ‎Risk‏ ‎Estimation‏ ‎Challenges

Estimating ‎the‏ ‎risk ‎posed‏ ‎by ‎the ‎Terminator ‎toolkit ‎is‏ ‎complex‏ ‎due ‎to‏ ‎several ‎variables.‏ ‎These ‎include ‎the ‎evolving ‎nature‏ ‎of‏ ‎the‏ ‎toolkit, ‎the‏ ‎diversity ‎and‏ ‎operational ‎scale‏ ‎of‏ ‎the ‎threat‏ ‎actors ‎employing ‎it, ‎and ‎the‏ ‎range ‎of‏ ‎potential‏ ‎targets. ‎The ‎exact‏ ‎success ‎rate‏ ‎of ‎Terminator ‎in ‎compromising‏ ‎organizations‏ ‎is ‎difficult‏ ‎to ‎quantify.‏ ‎However, ‎its ‎technical ‎sophistication, ‎coupled‏ ‎with‏ ‎the ‎increasing‏ ‎popularity ‎of‏ ‎BYOVD ‎techniques ‎among ‎threat ‎actors,‏ ‎suggests‏ ‎a‏ ‎growing ‎threat

The‏ ‎Evolution ‎and‏ ‎Variants ‎of‏ ‎Terminator

Since‏ ‎its ‎initial‏ ‎release, ‎multiple ‎variants ‎of ‎the‏ ‎Terminator ‎tool‏ ‎have‏ ‎been ‎developed, ‎including‏ ‎open-source ‎versions‏ ‎and ‎those ‎written ‎in‏ ‎different‏ ‎programming ‎languages‏ ‎such ‎as‏ ‎C# ‎(SharpTerminator) ‎and ‎Nim ‎(Ternimator).‏ ‎These‏ ‎variants ‎aim‏ ‎to ‎reproduce‏ ‎the ‎original ‎technique ‎or ‎offer‏ ‎cross-platform‏ ‎support,‏ ‎potentially ‎circumventing‏ ‎static ‎detections‏ ‎or ‎heuristic‏ ‎models.

Real-World‏ ‎Attacks ‎and‏ ‎Implications

The ‎use ‎of ‎the ‎Terminator‏ ‎tool ‎and‏ ‎its‏ ‎variants ‎in ‎real-world‏ ‎attacks ‎has‏ ‎been ‎documented, ‎including ‎a‏ ‎notable‏ ‎attack ‎on‏ ‎a ‎healthcare‏ ‎organization ‎on ‎December ‎15, ‎2023.‏ ‎In‏ ‎this ‎attack,‏ ‎the ‎perpetrators‏ ‎attempted ‎to ‎execute ‎a ‎PowerShell‏ ‎command‏ ‎to‏ ‎download ‎a‏ ‎text ‎file‏ ‎from ‎a‏ ‎C2‏ ‎server, ‎which‏ ‎was ‎designed ‎to ‎install ‎the‏ ‎XMRig ‎cryptominer‏ ‎on‏ ‎the ‎targeted ‎system.

Common‏ ‎techniques ‎used‏ ‎by ‎attackers ‎to ‎abuse‏ ‎the‏ ‎Terminator ‎tool:

1. Exploiting‏ ‎Legitimate ‎but‏ ‎Vulnerable ‎Drivers

Attackers ‎implant ‎a ‎legitimate‏ ‎driver,‏ ‎which ‎is‏ ‎vulnerable, ‎into‏ ‎a ‎targeted ‎system ‎and ‎then‏ ‎exploit‏ ‎the‏ ‎vulnerable ‎driver‏ ‎to ‎perform‏ ‎malicious ‎actions.‏ ‎This‏ ‎is ‎the‏ ‎core ‎principle ‎of ‎BYOVD ‎attacks,‏ ‎where ‎the‏ ‎Terminator‏ ‎tool ‎leverages ‎vulnerabilities‏ ‎in ‎drivers‏ ‎such ‎as ‎zam64.sys ‎(Zemana‏ ‎Anti-Logger)‏ ‎or ‎zamguard64.sys‏ ‎(Zemana ‎Anti-Malware)‏ ‎to ‎gain ‎kernel ‎privileges ‎and‏ ‎execute‏ ‎attacker-provided ‎code‏ ‎in ‎kernel‏ ‎context

2. Kernel-Level ‎Privilege ‎Escalation

Successful ‎exploitation ‎allows‏ ‎attackers‏ ‎to‏ ‎achieve ‎kernel-level‏ ‎privilege ‎escalation,‏ ‎granting ‎them‏ ‎the‏ ‎highest ‎level‏ ‎of ‎access ‎and ‎control ‎over‏ ‎system ‎resources.‏ ‎This‏ ‎escalated ‎privilege ‎is‏ ‎leveraged ‎by‏ ‎disabling ‎endpoint ‎security ‎software‏ ‎or‏ ‎evading ‎their‏ ‎detection, ‎thereby‏ ‎enabling ‎attackers ‎to ‎engage ‎in‏ ‎malicious‏ ‎activities ‎without‏ ‎any ‎obstruction

3. Disabling‏ ‎Security ‎Solutions

Once ‎endpoint ‎security ‎defenses‏ ‎are‏ ‎compromised,‏ ‎attackers ‎are‏ ‎free ‎to‏ ‎disable ‎antivirus‏ ‎and‏ ‎Endpoint ‎Detection‏ ‎and ‎Response ‎(EDR) ‎processes, ‎deploy‏ ‎additional ‎malware,‏ ‎or‏ ‎perform ‎other ‎malicious‏ ‎activities ‎without‏ ‎detection. ‎The ‎Terminator ‎tool‏ ‎specifically‏ ‎targets ‎and‏ ‎terminates ‎processes‏ ‎associated ‎with ‎security ‎solutions, ‎effectively‏ ‎blinding‏ ‎them ‎to‏ ‎ongoing ‎attacks

4. Use‏ ‎of ‎IOCTL ‎Codes

The ‎Terminator ‎tool‏ ‎and‏ ‎its‏ ‎variants ‎abuse‏ ‎IOCTL ‎(Input/Output‏ ‎Control) ‎codes‏ ‎to‏ ‎request ‎functionalities‏ ‎from ‎the ‎vulnerable ‎driver, ‎such‏ ‎as ‎attempting‏ ‎to‏ ‎terminate ‎targeted ‎processes.‏ ‎This ‎involves‏ ‎sending ‎specific ‎IOCTL ‎codes‏ ‎along‏ ‎with ‎parameters‏ ‎like ‎the‏ ‎process ‎ID ‎of ‎a ‎running‏ ‎process‏ ‎to ‎manipulate‏ ‎the ‎driver’s‏ ‎behavior ‎to ‎the ‎attacker’s ‎advantage

5. Administrative‏ ‎Privileges‏ ‎and‏ ‎UAC ‎Bypass

To‏ ‎abuse ‎the‏ ‎driver ‎effectively,‏ ‎a‏ ‎threat ‎actor‏ ‎would ‎need ‎administrative ‎privileges ‎and‏ ‎a ‎User‏ ‎Account‏ ‎Control ‎(UAC) ‎bypass,‏ ‎or ‎they‏ ‎would ‎need ‎to ‎convince‏ ‎a‏ ‎user ‎to‏ ‎accept ‎a‏ ‎UAC ‎prompt. ‎This ‎requirement ‎highlights‏ ‎the‏ ‎importance ‎of‏ ‎privilege ‎escalation‏ ‎tactics ‎and ‎social ‎engineering ‎in‏ ‎the‏ ‎successful‏ ‎deployment ‎of‏ ‎the ‎Terminator‏ ‎tool

6. Evading ‎Detection

Attackers‏ ‎have‏ ‎evolved ‎their‏ ‎techniques ‎to ‎evade ‎detection ‎by‏ ‎security ‎solutions.‏ ‎For‏ ‎example, ‎the ‎Terminator‏ ‎tool ‎attempts‏ ‎to ‎emulate ‎legitimate ‎protocol/file‏ ‎headers‏ ‎to ‎bypass‏ ‎security ‎measures,‏ ‎although ‎this ‎has ‎been ‎met‏ ‎with‏ ‎varying ‎degrees‏ ‎of ‎success.‏ ‎The ‎use ‎of ‎legitimate ‎protocols‏ ‎and‏ ‎services‏ ‎as ‎command-and-control‏ ‎(C& ‎C)‏ ‎servers ‎or‏ ‎communication‏ ‎channels ‎is‏ ‎another ‎tactic ‎to ‎cover ‎their‏ ‎tracks

7. Leveraging ‎Public‏ ‎Platforms‏ ‎and ‎Protocols

Attackers ‎also‏ ‎use ‎legitimate‏ ‎platforms ‎and ‎protocols, ‎such‏ ‎as‏ ‎instant ‎messengers‏ ‎(IMs) ‎and‏ ‎free ‎email ‎services, ‎to ‎communicate‏ ‎with‏ ‎compromised ‎systems‏ ‎and ‎maintain‏ ‎control ‎over ‎their ‎targets. ‎This‏ ‎technique‏ ‎helps‏ ‎to ‎blend‏ ‎malicious ‎traffic‏ ‎with ‎legitimate‏ ‎network‏ ‎activity, ‎making‏ ‎detection ‎more ‎challenging

Читать: 2+ мин
logo Overkill Security

SharpADWS

SharpADWS is ‎a‏ ‎tool ‎designed ‎for ‎Red ‎Team‏ ‎operations ‎that‏ ‎focuses‏ ‎on ‎reconnaissance ‎and‏ ‎exploitation ‎of‏ ‎Active ‎Directory ‎(AD) ‎environments‏ ‎through‏ ‎the ‎Active‏ ‎Directory ‎Web‏ ‎Services ‎(ADWS) ‎protocol. ‎Unlike ‎traditional‏ ‎methods‏ ‎of ‎interacting‏ ‎with ‎Active‏ ‎Directory, ‎which ‎often ‎use ‎the‏ ‎Lightweight‏ ‎Directory‏ ‎Access ‎Protocol‏ ‎(LDAP), ‎SharpADWS‏ ‎leverages ‎ADWS‏ ‎to‏ ‎perform ‎its‏ ‎operations.

ADWS ‎is ‎a ‎web ‎service‏ ‎that ‎is‏ ‎automatically‏ ‎enabled ‎when ‎Active‏ ‎Directory ‎Domain‏ ‎Services ‎(ADDS) ‎is ‎installed,‏ ‎making‏ ‎it ‎universally‏ ‎available ‎across‏ ‎domain ‎environments. ‎It ‎operates ‎on‏ ‎TCP‏ ‎port ‎9389‏ ‎and ‎uses‏ ‎the ‎SOAP ‎protocol ‎for ‎communication.‏ ‎One‏ ‎of‏ ‎the ‎key‏ ‎advantages ‎of‏ ‎using ‎ADWS‏ ‎is‏ ‎that ‎it‏ ‎is ‎relatively ‎unknown ‎and ‎underutilized‏ ‎for ‎LDAP‏ ‎post-exploitation,‏ ‎which ‎can ‎make‏ ‎activities ‎carried‏ ‎out ‎through ‎it ‎less‏ ‎detectable‏ ‎by ‎common‏ ‎monitoring ‎tools.

SharpADWS‏ ‎can ‎perform ‎various ‎actions ‎without‏ ‎directly‏ ‎communicating ‎with‏ ‎the ‎LDAP‏ ‎server. ‎Instead, ‎LDAP ‎queries ‎are‏ ‎wrapped‏ ‎in‏ ‎SOAP ‎messages‏ ‎and ‎sent‏ ‎to ‎the‏ ‎ADWS‏ ‎server, ‎which‏ ‎then ‎unpacks ‎and ‎forwards ‎them‏ ‎to ‎the‏ ‎LDAP‏ ‎server. ‎This ‎can‏ ‎result ‎in‏ ‎LDAP ‎queries ‎appearing ‎to‏ ‎originate‏ ‎from ‎the‏ ‎local ‎address‏ ‎127.0.0.1 ‎in ‎logs, ‎which ‎might‏ ‎be‏ ‎overlooked ‎by‏ ‎security ‎systems.

The‏ ‎tool ‎implements ‎several ‎protocols, ‎including‏ ‎MS-ADDM,‏ ‎MS-WSTIM,‏ ‎and ‎MS-WSDS,‏ ‎and ‎allows‏ ‎for ‎operations‏ ‎such‏ ‎as ‎enumeration,‏ ‎pulling ‎results, ‎renewing, ‎getting ‎status,‏ ‎and ‎releasing‏ ‎enumeration‏ ‎contexts. ‎SharpADWS ‎can‏ ‎also ‎be‏ ‎used ‎to ‎modify ‎Active‏ ‎Directory‏ ‎data, ‎such‏ ‎as ‎granting‏ ‎DCSync ‎privileges ‎to ‎an ‎account‏ ‎for‏ ‎domain ‎persistence‏ ‎or ‎enabling‏ ‎the ‎«Do ‎not ‎require ‎kerberos‏ ‎preauthentication»‏ ‎option‏ ‎for ‎an‏ ‎account ‎to‏ ‎perform ‎an‏ ‎AS-REP‏ ‎Roasting ‎attack.

So,‏ ‎SharpADWS ‎is ‎a ‎sophisticated ‎tool‏ ‎for ‎Red‏ ‎Teams‏ ‎that ‎provides ‎an‏ ‎alternative ‎way‏ ‎to ‎interact ‎with ‎Active‏ ‎Directory‏ ‎using ‎ADWS,‏ ‎potentially ‎allowing‏ ‎for ‎stealthier ‎reconnaissance ‎and ‎exploitation‏ ‎activities‏ ‎within ‎a‏ ‎target ‎domain‏ ‎environment

Читать: 1+ мин
logo Snarky Security

T-Mobile and Verizon employees report receiving $300 offers for facilitating unauthorized SIM swaps.

📌Bribery ‎Offers‏ ‎to ‎Telecom ‎Employees: ‎T-Mobile ‎and‏ ‎Verizon ‎employees,‏ ‎including‏ ‎former ‎staff, ‎have‏ ‎reported ‎receiving‏ ‎unsolicited ‎messages ‎offering ‎$300‏ ‎for‏ ‎each ‎SIM‏ ‎swap ‎they‏ ‎facilitate. ‎These ‎messages ‎were ‎shared‏ ‎on‏ ‎Reddit, ‎showcasing‏ ‎screenshots ‎of‏ ‎the ‎texts.

📌Method ‎of ‎Contact: The ‎attackers‏ ‎used‏ ‎various‏ ‎communication ‎methods,‏ ‎including ‎text‏ ‎messages ‎and‏ ‎encrypted‏ ‎platforms ‎like‏ ‎Telegram, ‎to ‎contact ‎the ‎employees.‏ ‎The ‎messages‏ ‎often‏ ‎claimed ‎to ‎have‏ ‎obtained ‎the‏ ‎employees' ‎contact ‎information ‎from‏ ‎company‏ ‎directories.

📌Potential ‎Insider‏ ‎Threats: The ‎situation‏ ‎raises ‎concerns ‎about ‎insider ‎threats‏ ‎within‏ ‎telecom ‎companies,‏ ‎as ‎the‏ ‎messages ‎targeted ‎current ‎and ‎former‏ ‎employees‏ ‎who‏ ‎might ‎have‏ ‎access ‎to‏ ‎the ‎systems‏ ‎needed‏ ‎to ‎execute‏ ‎SIM ‎swaps.

📌Company ‎Responses: ‎Both ‎T-Mobile‏ ‎and ‎Verizon‏ ‎are‏ ‎aware ‎of ‎these‏ ‎incidents. ‎T-Mobile‏ ‎has ‎stated ‎that ‎there‏ ‎was‏ ‎no ‎system‏ ‎breach ‎involved‏ ‎and ‎that ‎they ‎are ‎investigating‏ ‎the‏ ‎messages. ‎Verizon’s‏ ‎response ‎is‏ ‎currently ‎not ‎detailed ‎in ‎the‏ ‎reports.

📌Impact‏ ‎of‏ ‎SIM ‎Swapping: SIM‏ ‎swapping ‎can‏ ‎lead ‎to‏ ‎significant‏ ‎security ‎breaches,‏ ‎allowing ‎attackers ‎to ‎bypass ‎two-factor‏ ‎authentication, ‎access‏ ‎personal‏ ‎and ‎financial ‎information,‏ ‎and ‎potentially‏ ‎lead ‎to ‎financial ‎fraud‏ ‎and‏ ‎identity ‎theft.

📌Preventive‏ ‎Measures ‎and‏ ‎Recommendations: It ‎is ‎recommended ‎that ‎telecom‏ ‎companies‏ ‎enhance ‎their‏ ‎internal ‎security‏ ‎measures ‎and ‎employee ‎verification ‎processes‏ ‎to‏ ‎prevent‏ ‎such ‎incidents.‏ ‎Employees ‎are‏ ‎advised ‎to‏ ‎report‏ ‎any ‎suspicious‏ ‎activities ‎and ‎not ‎engage ‎with‏ ‎such ‎offers.

Читать: 2+ мин
logo Snarky Security

Empty S3 bucket makes your AWS bill explode

The ‎article discusses‏ ‎a ‎significant ‎issue ‎where ‎an‏ ‎empty, ‎private‏ ‎AWS‏ ‎S3 ‎bucket ‎can‏ ‎lead ‎to‏ ‎unexpectedly ‎high ‎AWS ‎bills‏ ‎due‏ ‎to ‎unauthorized‏ ‎incoming ‎requests.

This‏ ‎case ‎study ‎serves ‎as ‎a‏ ‎cautionary‏ ‎tale ‎about‏ ‎the ‎potential‏ ‎financial ‎risks ‎associated ‎with ‎AWS‏ ‎services,‏ ‎particularly‏ ‎S3, ‎and‏ ‎underscores ‎the‏ ‎importance ‎of‏ ‎understanding‏ ‎AWS ‎billing‏ ‎practices ‎and ‎configuring ‎AWS ‎services‏ ‎securely ‎to‏ ‎avoid‏ ‎unexpected ‎charges.

📌Unexpected ‎High‏ ‎Costs: ‎The‏ ‎author ‎experienced ‎a ‎sudden‏ ‎spike‏ ‎in ‎his‏ ‎AWS ‎bill,‏ ‎amounting ‎to ‎over ‎$1,300, ‎due‏ ‎to‏ ‎nearly ‎100,000,000‏ ‎S3 ‎PUT‏ ‎requests ‎executed ‎within ‎a ‎single‏ ‎day‏ ‎on‏ ‎an ‎empty‏ ‎S3 ‎bucket‏ ‎he ‎had‏ ‎set‏ ‎up ‎for‏ ‎testing.

📌Source ‎of ‎Requests: Initially, ‎AWS ‎does‏ ‎not ‎log‏ ‎requests‏ ‎executed ‎against ‎S3‏ ‎buckets ‎by‏ ‎default. ‎The ‎author ‎had‏ ‎to‏ ‎enable ‎AWS‏ ‎CloudTrail ‎logs‏ ‎to ‎identify ‎the ‎source ‎of‏ ‎the‏ ‎requests. ‎It‏ ‎was ‎found‏ ‎that ‎misconfigured ‎systems ‎were ‎attempting‏ ‎to‏ ‎store‏ ‎data ‎in‏ ‎his ‎private‏ ‎S3 ‎bucket.

📌Billing‏ ‎for‏ ‎Unauthorized ‎Requests: AWS‏ ‎charges ‎for ‎unauthorized ‎incoming ‎requests‏ ‎to ‎S3‏ ‎buckets.‏ ‎This ‎was ‎confirmed‏ ‎during ‎the‏ ‎author’s ‎communication ‎with ‎AWS‏ ‎support,‏ ‎highlighting ‎a‏ ‎critical ‎billing‏ ‎policy ‎where ‎the ‎bucket ‎owner‏ ‎pays‏ ‎for ‎incoming‏ ‎requests ‎regardless‏ ‎of ‎their ‎authorization ‎status.

📌Prevention ‎and‏ ‎Protection: The‏ ‎article‏ ‎notes ‎that‏ ‎there ‎is‏ ‎no ‎straightforward‏ ‎way‏ ‎to ‎prevent‏ ‎such ‎incidents ‎other ‎than ‎deleting‏ ‎the ‎bucket.‏ ‎AWS‏ ‎does ‎not ‎allow‏ ‎the ‎bucket‏ ‎to ‎be ‎protected ‎by‏ ‎services‏ ‎like ‎CloudFront‏ ‎or ‎WAF‏ ‎when ‎it ‎is ‎accessed ‎directly‏ ‎through‏ ‎the ‎S3‏ ‎API.

📌AWS ‎Investigation: Following‏ ‎the ‎incident, ‎AWS ‎began ‎investigating‏ ‎the‏ ‎issue,‏ ‎as ‎indicated‏ ‎by ‎a‏ ‎tweet ‎from‏ ‎Jeff‏ ‎Barr, ‎a‏ ‎prominent ‎AWS ‎evangelist. ‎This ‎suggests‏ ‎that ‎AWS‏ ‎is‏ ‎aware ‎of ‎the‏ ‎potential ‎for‏ ‎such ‎problems ‎and ‎may‏ ‎be‏ ‎considering ‎ways‏ ‎to ‎address‏ ‎them.

Показать еще

Подарить подписку

Будет создан код, который позволит адресату получить бесплатный для него доступ на определённый уровень подписки.

Оплата за этого пользователя будет списываться с вашей карты вплоть до отмены подписки. Код может быть показан на экране или отправлен по почте вместе с инструкцией.

Будет создан код, который позволит адресату получить сумму на баланс.

Разово будет списана указанная сумма и зачислена на баланс пользователя, воспользовавшегося данным промокодом.

Добавить карту
0/2048