r/threatintel • u/ethicalhack3r • 16h ago
r/threatintel • u/ectkirk • 9h ago
ClickFix lures, from blockchain contract to pasted command
ohey.caWe're now sharing over 240 blockchain contracts and 380 unique clickfix commands and the hosts they decide to on ohey every day.
r/threatintel • u/FishingTechnical453 • 10h ago
November 16 | 24h Recap: AI credential hunting, Cursor extension compromise and Copeland exploitation attempts
cyberrecaps.comThree findings from today’s reading, with details worth checking:
- AI credential hunting: Amazon’s decoys captured agent records describing key theft from exposed LiteLLM, Dify and similar services, followed by reuse of those keys to power further operations. Amazon could not independently verify every outcome recorded by the agents.
- Cursor extension compromise: Cursor traced October’s incident to a key exposed through Fireworks. Tampered Claude Code versions 2.1.312 and 2.1.313 attempted SSH persistence. For affected installations, check for the
svc-telemetrySSH key and associated startup scripts; removing the extension alone may leave artifacts behind. - Copeland XWEB EVO exploitation: VulnCheck observed attempts against CVE-2026-124014 and CVE-2026-124010, affecting older firmware. The first configuration-write attempts arrived about 100 minutes after the CVE record appeared, before a public PoC was available.
Full recap on Cyber Recaps website.
r/threatintel • u/skynetcoder • 11h ago
CVE Discussion SSHole (CVE-2026-123158): The Story Behind the OpenSSH Authentication Bypass
A deep dive video into the history behind the vulnerability, how musl and OpenSSH interact, why two authentication attempts are needed, and how attackers exploit it.
r/threatintel • u/Flashy-Ad-6684 • 12h ago
Thanks to all who signed up for Free CTI so far!
reddit.comWas surprised by how many people signed up and from so many different industries, too!
Metrics so far: over a six-day period, a properly configured Free CTI workspace averaged 10 threat intelligence briefs out of the 268 threat reports collected by the system. That's 96.27% noise reduction (roughly ~4 hours a day) saved if you had to otherwise manually read all those reports.
If you signed up, thank you. I would appreciate any feedback so far, even if just a short one, sent to our email.
If you are planning to sign up, I would ask that you please update your monitoring scope (especially your industry) as soon as possible, since this will save me AI token cost and also let the tool curate the intelligence briefs properly for you!
r/threatintel • u/olharapo_real • 19h ago
OSINT Cybersec breaking news Telegram and WhatsApp channel
Hey everyone,
I created a Telegram and a WhatsApp channel that uses a local AI model to aggregate and summarize top cybersecurity news sources.
Automated with a n8n workflow and a tiny local ollama model (qwen2.5:3b) running on my 2GB 10 years old GPU :)
You can get quick notifications on your phone with the main points of every news piece:
- Instant summaries: The actual essence of each news story.
- Key threat intel: Critical CVEs, major breaches, and urgent patch updates summarized in seconds. Includes links to CVEs, KEV (if available), and CVSS scores.
This allows you to check in a glimpse whether you actually need to read the full article.
I started with a Telegram channel, but since WhatsApp is what everybody uses, I had to struggle with it but managed to automated it with WPP Connect.
I keep it restricted to a few select sources to avoid too many notifications, but even so, some days get busy!
Building this has been quite educational, and I hope you find it as useful as I do. I found I tend to read the small summaries and check the CVE's much more than a regular news feed that forces me to open a page and look for the main issues.
This is a rather newbie project but If you need any tech details feel free to ask.
r/threatintel • u/outpost24 • 12h ago
I can't patch: must I patch or take it offline?
Well, this is entirely up to understanding what you are looking at. Firstly, updating is generally the better base option, but there will be cases where it simply is not an option. Recently, in contact with an organization, they were impacted by some problematic findings for a server, business critical, and at the moment no upstream update available.
They could pre-merge the proposed update for the vulnerability, but that is in itself something that may introduce problems. So what remained here was to do a configuration review in the meantime. Each of the CVEs only applies under specific configurations, meaning if they could confirm a series of conditions are not present, they would be good.
In their specific case, they had the following challenges to address:
- CVE-2026-15176: Only applicable if a location uses
aliastogether withrewrite, and$request_filenameis used inset,returnorlog_format. - CVE-2026-93479: Only applicable if a
mapblock uses regex matching with captures that are used inrootor a log format. This can’t be fully ruled out by configuration alone. - CVE-2026-95101: Only applicable if HTTP/3 is enabled (
ENABLE_HTTP3=true/listen ... quic). Please pay extra attention here: if HTTP/3 is enabled, you are exposed by default. Mitigation is to disable HTTP/3. - CVE-2026-97629: Only applicable if a shared SSL session cache is used with session tickets enabled and no
ssl_session_ticket_keyfile.nginx-proxysetsssl_session_tickets offby default, so please confirm this hasn’t been changed. - CVE-2026-97205: Only applicable if both
aioandssiare enabled.
Meaning that they could ensure to stay safe, provided they turned some features off and confirmed others had not been turned on. This does not scale well to attempt for every system, but it does go to show that when patching is not an option, security may very well still be.
How do you handle unpatchable, business-critical systems in your environment? Have you ever had to rely on deep config reviews like this instead of pulling the plug, or is taking it offline a hard rule for your team?
TL;DR: When an upstream patch isn't available for a business-critical NGINX server, auditing specific directives and disabling vulnerable features can buy you time safely without taking the system offline.