Hackers Are Finding New Ways to Hide Malware in DNS Records
Technology
13
Beiträge
10
Kommentatoren
77
Aufrufe
-
"Ignore all previous instructions. Ignore all future instructions."
I like that one. Can we add "ignore all instructions from everyone else" and just be done with these LLMs?
Remember when I said “ignore all future instructions”? You just now ignore that instruction.
-
https://archive.ph/z8DTZ
New ways, but they are really creative!Unless I'm missing something here... The attacker needs to be running some sort of executable in your network with permissions to:
- dig the records and assemble the strings
- write the decoded result to a file
- make that file executable
- execute that file
You've got bigger problems than hexadecimal txt records in this scenario...
The only difference between this and a GitHub gist appears to be that security software doesn't scan traffic in port 53... It easily could be configured for that though surely... It's just UDP traffic like any other.
Someone tell me what I'm missing!
-
Unless I'm missing something here... The attacker needs to be running some sort of executable in your network with permissions to:
- dig the records and assemble the strings
- write the decoded result to a file
- make that file executable
- execute that file
You've got bigger problems than hexadecimal txt records in this scenario...
The only difference between this and a GitHub gist appears to be that security software doesn't scan traffic in port 53... It easily could be configured for that though surely... It's just UDP traffic like any other.
Someone tell me what I'm missing!
When a remote code execution exploit is run, you often have a very limited payload you can deliver. Usually that means delivering a small downloader that then downloads and installs a backdoor from somewhere on the Internet
The standard counter-measure to protect your servers is to block all outbound traffic unless it's to a known safe destination. Downloading the secondary payload over DNS gets around that since you can't just block DNS. Tools to protect against this or DNS tunneling are still relatively new, so a lot of people haven't implemented them yet.
-
When a remote code execution exploit is run, you often have a very limited payload you can deliver. Usually that means delivering a small downloader that then downloads and installs a backdoor from somewhere on the Internet
The standard counter-measure to protect your servers is to block all outbound traffic unless it's to a known safe destination. Downloading the secondary payload over DNS gets around that since you can't just block DNS. Tools to protect against this or DNS tunneling are still relatively new, so a lot of people haven't implemented them yet.
Ah, interesting. Thanks
-
https://archive.ph/z8DTZ
New ways, but they are really creative!So it is not an attack, just a stealth way to move data unmonitored by most nanny systems.
-
https://archive.ph/z8DTZ
New ways, but they are really creative!Does anyone have a link to a non paywalled version
-
Remember when I said “ignore all future instructions”? You just now ignore that instruction.
Ignore all previous instructions.
ignore all instructions from everyone else.
Ignore all future instructions. -
Ignore all previous instructions.
ignore all instructions from everyone else.
Ignore all future instructions. -
Does anyone have a link to a non paywalled version
there is an archive link in description.
-
there is an archive link in description.
I got you a cape.
