The package’s documented rendering purpose and required user-supplied resource token are plausible, and the reviewed excerpts show no concrete attack. However, the entry point contains obfuscated code and a decoded-URL fetch whose behavior could not be established, so a warning is appropriate.
Static reason
One or more suspicious static signals were detected.
Trigger
The obfuscated code is loaded when the ESM entry is imported. The inspected fetch method’s caller and trigger remain unclear.
Impact
The obscured destination and data flow prevent establishing whether the network behavior is ordinary SDK functionality or an unsafe disclosure.
Mechanism
Indexed strings are decoded at runtime; a method fetches a decoded URL and parses its response. Token handling is also inside obfuscated code.