preview
Text transcription
A Tweet by lifcc @mylifcc
Translated from Chinese by Grok
Someone discovered an utterly absurd JavaScript obfuscation technique: by stuffing the code with a ton of function names related to biological weapons, poisons, and lethal doses, it causes AI to refuse analyzing the code due to safety restrictions.
Security researcher veritas, while analyzing browser fingerprinting scripts, came across a piece of JavaScript from a domain linked to ServicePipe, brimming with extremely bizarre function names:
computeRicinLethalDosageForWaterSupply
calculateDeadlyLethalSuicideAspirinDosage
Just looking at the names, it feels like you’re studying biochemical weapons. But in reality, this code is simply collecting browser fingerprint data, including User-Agent, GPU, Canvas, and other info.
Text transcription
A Tweet by lifcc @mylifcc
Translated from Chinese by Grok
Someone discovered an utterly absurd JavaScript obfuscation technique: by stuffing the code with a ton of function names related to biological weapons, poisons, and lethal doses, it causes AI to refuse analyzing the code due to safety restrictions.
Security researcher veritas, while analyzing browser fingerprinting scripts, came across a piece of JavaScript from a domain linked to ServicePipe, brimming with extremely bizarre function names:
computeRicinLethalDosageForWaterSupply
calculateDeadlyLethalSuicideAspirinDosage
Just looking at the names, it feels like you’re studying biochemical weapons. But in reality, this code is simply collecting browser fingerprint data, including User-Agent, GPU, Canvas, and other info.