Loading malware…
BeeStealer is an information-stealing malware family that has been observed collecting locally stored artifacts from AI-assisted development tools. Its collection scope includes data that may contain session access and refresh tokens, API keys and other secrets in Model Context Protocol configurations, prompt and conversation histories, project metadata, and connected-service settings. Theft of these artifacts can enable session hijacking, unauthorized use of AI-service accounts, API-consumption abuse, exposure of development context and source code, and compromise of connected enterprise services. BeeStealer illustrates the use of remotely managed collection rules, allowing operators to extend targeting to additional application artifacts on systems already compromised by the stealer. It is associated with the broader infostealer ecosystem targeting endpoint-resident data rather than exploiting vulnerabilities in AI agents directly.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
1 distinct technique documented for this family, organized by ATT&CK tactic.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Information-stealing malware cited as part of the expanding use of stealers to harvest local AI coding-agent artifacts.
Named as an information stealer illustrating the growing theft of locally stored AI coding-agent artifacts.
Lower-prevalence information-stealer family included among malware targeting data from AI-assisted development tools.
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.