51–60 of 316 posts
Turns out any site that allows users to submit and retrieve data can be abused in the same way: - FacebookDrive: "Store files as base64 facebook posts" - TwitterDrive: "Store files as base64 tweets" - SoundCloudDrive: "Store files as mp3 audio" - WikipediaDrive: "Store files in wikipedia article histories"
Earlier quoted context omitted.
I think that video compression might make this not a viable technique. Artifacts would destroy the hidden data, right?
Couldn't you also embed data through sound? Upload a video of a monkey at the zoo but you insert ultrasound with encoded data. something like this but far more mundane https://www.youtube.com/watch?v=yLNpy62jIFk
Others in these comments have also suggested steganography in both the video and audio streams. The problem with that is that when you retrieve a video from YouTube, you never get the original version back. You only get a lossy re-encoded version, and the very definition of lossy encoding is to toss out details that humans can't (or wouldn't easily) perceive, including ultra-sonic audio.
Seems like a great way to get your account closed for abuse!
You'd be surprised how much YouTube lets you upload. I've been uploading 2-3 hours of content a day every day for the past few years. On the same account too. I have fewer than 10 subscribers lol.
Turns out any site that allows users to submit and retrieve data can be abused in the same way: - FacebookDrive: "Store files as base64 facebook posts" - TwitterDrive: "Store files as base64 tweets" - SoundCloudDrive: "Store files as mp3 audio" - WikipediaDrive: "Store files in wikipedia article histories"
See also https://github.com/qntm/base2048 . "Base2048 is a binary encoding optimised for transmitting data through Twitter."
I can't wait until malware uses this as C2
Seems pretty fragile. Google taking down your channel would be enough to disarm your malware.
(plus using more than one tld)
Earlier quoted context omitted.
See also https://github.com/qntm/base2048 . "Base2048 is a binary encoding optimised for transmitting data through Twitter."
Still need around 30,000 more unicode characters for this to work.
Years ago when Amazon had unlimited photo storage, you could “hide” gigabytes of data behind a 1px gif (literally concatenation together) so that it wouldn’t count against your quota.
Earlier quoted context omitted.
See also https://github.com/qntm/base2048 . "Base2048 is a binary encoding optimised for transmitting data through Twitter."
Still need around 30,000 more unicode characters for this to work.