Podcast Detail

Phishing Collects MX Records; Java4Shell OpenJDK RCE (CVE-2026-114938); Optimizely Magecart Compromise (Nov 18 2026)

If you are not able to play the podcast using the player below: Use this direct link to the audio file: https://traffic.libsyn.com/securitypodcast/10184.mp3

Podcast Logo
Phishing Collects MX Records; Java4Shell OpenJDK RCE (CVE-2026-114938); Optimizely Magecart Compromise (Nov 18 2026)
00:00

My Next Class

Click HERE to learn more about classes Johannes is teaching for SANS

Jan Kopriva describes a phishing kit that collects MX records, Calif discloses Java4Shell remote code execution in OpenJDK's Base64 decoder, and an Optimizely compromise spread Magecart-style malware to major websites.

A Phishing Page Interested in MX Records
Jan Kopriva of the SANS Internet Storm Center describes a phishing page that customizes itself based on the victim's email domain, then uses JavaScript to perform a DNS-over-HTTPS (DoH) lookup of the domain's Mail Exchange (MX) records via Google DNS. The MX records are stored with the stolen username and password rather than used to customize the page.
https://isc.sans.edu/diary/A+phishing+page+interested+in+MX+records/33526/

Java4Shell: Write Once, RCE Everywhere
Calif, the firm behind PHP2Shell, disclosed Java4Shell (CVE-2026-114938), a memory-corruption bug in OpenJDK's Base64 decoder on x86-64 CPUs that support the AVX-512 VBMI extension; ARM processors are not affected. The flaw can allow unauthenticated remote code execution in applications such as Keycloak, and can also leak memory in a manner similar to Heartbleed; Oracle released a patch in its November Critical Security Patch Update.
https://calif.io/java4shell/
https://www.oracle.com/security-alerts/cspunov2026.html

Optimizely Compromise
Attackers compromised Optimizely, a JavaScript experimentation platform used by many large websites, and swapped the distributed script for a Magecart-style payload that stole payment card and cryptocurrency wallet information. Report URI found the malware on sites belonging to 178 organizations, including HSBC and the BBC; Johannes suggests blocking optimizely.com and the .icu top-level domain.
https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/

My Upcoming Classes
https://www.sans.org/profiles/dr-johannes-ullrich

Podcast Transcript

 Hello and welcome to the Wednesday, November 18th, 2026
 edition of the SANS Internet Storm Center's Stormcast. My name is
 Johannes Ullrich, recording today from Jacksonville,
 Florida. And this episode is brought to you by the SANS.edu
 Undergraduate Certificate Program in Applied
 Cybersecurity. Well, in Diaries today we have Jan talk
 about yet another phishing attack. This one does have
 some interesting stuff with MX records. So the phishing page
 that the user is visiting is first of all customized based
 on the user's email domain. And then JavaScript is being
 used to actually do a DNS lookup over HTTPS just by
 hitting the Google DNS endpoint. And that information
 is then included in the data being sent back to the
 phisher. So it's not used to customize the page. That's
 just done based on the domain name itself. It's just being
 basically stored with the username and password that the
 victim types in. My guess is that the attacker is trying to
 get the MX record as seen by the user. Sometimes
 organizations set up their email differently for users
 inside the network versus what you would see externally.
 Maybe they're trying to compare this a little bit and
 either to validate the information or just maybe to
 find some different spot where they could possibly log in. As
 the public mail server that's being advertised to everybody
 else may not actually accept the user's login information.
 That's my guess here at least. If anybody has any other
 insight, let me know. Now we have yet another super
 critical, this will end the world as we know it,
 vulnerability. And this time again discovered by Calif,
 the company that was also behind some of the work
 regarding PHP2Shell. They're calling it Java4Shell,
 not 2Shell in this particular case. The
 vulnerability affects base64 decoding. And a lot of web
 applications, for example, for cookie values and the like use
 base64. So web applications certainly are exposed here. In
 order to be vulnerable, your CPU also has to support the
 AVX-512 VBMI extension. And that was originally released
 by Intel 12 years ago. So you can assume that most of your
 x86 CPUs, AMD supports it as well, are vulnerable to this
 particular buffer overflow. Anything ARM or such is not
 vulnerable. Also emulators and such tend to be not vulnerable
 according to some of the write -ups I've seen. But this was
 just released sort of about an hour before I record this.
 Oracle has released also a patch for this. Today as part
 of their monthly critical patch update. So a patch is
 available. Yes, apply it. And unless you don't do base64 and
 you don't use any x86 CPUs, which is unlikely for the most
 part. They list a couple of applications like Keycloak,
 for example, that are vulnerable without
 authentication. The vulnerability itself, of
 course, does not require authentication. It's just a
 basic Java vulnerability. The question really only becomes
 at what point are you actually able to reach an endpoint that
 accepts a base64 encoded data that can be used to trigger
 this vulnerability. Calif also states that it's unlikely
 that there will be sort of a universal exploit. Similar to
 what we have seen sort of with PHP2Shell and such with
 these memory corruption vulnerabilities. It tends to
 be tricky to work out all the offsets. Now, there is also a
 memory leakage part to this vulnerability. Similar to the
 Heartbleed attack where random memory may be leaked.
 So even the non-remote code execution path could be an
 issue for you here in case you have any data on your servers
 that you want to keep a secret. And yesterday,
 Optimizely, a company that produces JavaScript that's
 used by many big websites in order to monitor how users are
 using their website, essentially optimize how the
 website works. Well, Optimizely was compromised and
 essentially what happened was sort of your standard Magecart
 attack. That's sort of how this attack is often
 described, where the attacker then swapped out the
 JavaScript being distributed by Optimizely for a version
 that was compromised. The compromised version did
 essentially include sort of JavaScript info stealers,
 meaning on the page the code showed up. They would look for
 payment card information, crypto wallet information, and
 the like on mobile devices. Apparently, it also created
 pop-ups, advertising malware, which, of course, may be more
 plausible for the user to install if it shows up on like
 hsbc.com or bbc.com. Those are some of the sites that were
 affected. Looks like around 167, I think they mentioned
 websites were affected by this. What can you do about it
 as a user? Maybe just block Optimizely.com, set up a DNS
 block list for this. I don't think it does anything for the
 user of the website. It's really more sort of for
 marketing and such on the back end of the website where this
 is being used. Also, many of the domains, the malicious
 domains, they use the .ICU top -level domain, haven't really
 seen much good from that domain. So that may be another
 thing that you maybe just want to block. And basically with
 that, you probably cut down quite a bit on malware noise
 and other log entries. So with these two stories, one other
 sort of critical Java vulnerability and then this
 Optimizely script infecting more than 100 big name brand
 website. The question that often comes up these days is,
 and a lot of this, of course, appears to be AI-fueled, like,
 for example, the Java story. What should I do to prevent
 this, to protect myself? Just a quick word of advice. At the
 end of the day, 5 o'clock, go home, walk your dog. If you
 don't have a dog, get a dog. But this is the new normal.
 This is not an emergency. Don't treat it as an emergency
 that there is a super critical Java vulnerability, for
 example, that, yes, you need to patch across your
 environment. As you come in the morning, set up a plan.
 Set up what you have to do first. Get that done. At 5 o
 'clock, go home. If you are a leader that sort of manages
 people that respond to these incidents, make sure your
 people have the right tools, the right resources. And, yes,
 don't keep them overnight. It's not going to make a
 difference. It's only to burn out your people, because a
 week from now, there will be probably another super critical
 vulnerability, and you want to still be around at that point.
 So, anyway, that's it for today. Thanks for listening,
 and talk to you again tomorrow. Bye.