Severity: HIGH · Priority: P2 — probable developer/build-system compromise, investigate on hit
These rules detect network activity from WeaselBiscuit, a JavaScript information-stealer documented by OpenSourceMalware in September 2026 and distributed through malicious npm packages. It is a lightweight stealer that reuses functionality from two known malware families (BeaverTail and OtterCookie); researchers note overlaps with tooling associated with North Korea's "Contagious Interview" campaign but treat that link as a hypothesis, not a confirmed attribution. WeaselBiscuit installs when a developer imports a malicious npm package, pulls its real payload from a remote hosting service, and runs it in memory without writing it to disk. It profiles the machine and harvests browser and Chrome-extension data, including cryptocurrency-wallet extensions, and takes operator commands from its control server. These rules watch for its data-upload and input-capture traffic and for connections to its known control server.
A hit indicates a machine on your network — likely a developer workstation or build system — is communicating with WeaselBiscuit's infrastructure, which strongly suggests infection. Treat it as a probable compromise: identify the machine and user, and because this stealer targets browser credentials, crypto-wallet extensions, and system information, treat those as exposed — rotate the credentials, tokens, and wallet material the machine could reach, from a known-clean device. Identify and remove the malicious npm package, audit the project's dependencies for other malicious packages, and — because the payload runs only in memory rather than on disk — do not rely on finding a malicious file to confirm or rule out infection; the network activity these rules detect may be the clearest evidence.