NewsLayer.com
NewsLayer PulseLIVEBTC$79,004-0.85%ETH$2,481-0.15%SOL$103.73-2.21%XRP$1.39-1.26%DOGE$0.0897+0.47%ADA$0.2204+0.84%Total Cap$2.81T-0.84%Layer Index43 Neutral

JSCeal Hides Crypto Malware in V8 Bytecode

JSCeal is a cryptocurrency stealer that Check Point Research has tracked since early 2025. Unlike most malware, it hides its code in a format that makes analysis much harder. Check Point presented its latest research at Black Hat USA…

Security Affairs

Publisher

Sep 7, 2026 at 10:27 AM UTC · 5 분 소요

JSCeal Hides Crypto Malware in V8 Bytecode
NewsLayer editorial artwork
번역 중…

JSCeal Hides Crypto Malware in V8 Bytecode

Pierluigi Paganini September 07, 2026

JSCeal hides crypto-stealing malware in V8 bytecode, but researchers built a tool to decompile it and expose its advanced theft capabilities.

JSCeal is a cryptocurrency stealer that Check Point Research has tracked since early 2025. Unlike most malware, it hides its code in a format that makes analysis much harder. Check Point presented its latest research at Black Hat USA 2026 and showed how its team built a tool that converts the hidden code into a form analysts can understand.

JSCeal uses a clever trick. Instead of delivering normal JavaScript, its creators compile the malware into V8 bytecode, the format that Chrome and Node.js use to run JavaScript efficiently. They then package the bytecode with a Node.js runtime that executes it.

The original JavaScript never reaches the victim’s computer. As a result, most tools designed to analyze JavaScript have little useful code to work with.

“JSCeal is a stealer delivered as compiled V8 bytecode (.jsc) and executed by a bundled Node.js runtime, targeting cryptocurrency applications (other vendors also tag it with the names WEEVILPROXY or MeadowLocust). ” states the report. “Unlike ordinary JavaScript malware, JSCeal reaches the analyst after two transformations have already removed much of the information that source-oriented tools depend on. First, the JavaScript is heavily obfuscated. Then it is compiled into V8’s internal bytecode representation and shipped as cached data rather than source code. The resulting format is version-specific, poorly served by mature reverse-engineering tooling, and unsuitable for most standard JavaScript deobfuscation workflows.”