Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
5 distinct techniques documented for this family, organized by ATT&CK tactic.
“BootNova also takes steps to keep its own communication out of sight. A module the researchers labeled RsaUtils decodes the hardcoded C2 address, along with the messages exchanged with the server, using Base64 and a character-shifting cipher, so the address doesn’t sit in plain text for anyone inspecting the app.”
After an app starts, it contacts remote infrastructure for instructions on whether to run, which destinations to load, how many browser views to open, and how they should behave.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An orchestration component within Papyrus that contacts command-and-control infrastructure to retrieve runtime instructions controlling execution, destinations, browser view counts, timing, targeting, retries, and interaction behavior.
Core orchestration component used by Papyrus to contact C2 infrastructure, retrieve remote configuration, and control hidden browser activity including enablement, timing, geographic targeting, retry behavior, number of webviews, destination URLs, and interaction logic.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.