Linux Bun Runtime Execution: bun_environment.js via node-parent process

Flags /node-launched /bun executions running bun_environment.js with an external runner release download URL.

FreeReviewedSigma · High · v5
Product
linux
Category
process_creation
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-11-25
Updated
2026-07-31

ATT&CK techniques

Initial Access → Execution
  1. Recon

  2. Resource Dev

  3. Persistence

  4. Priv Esc

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule identifies process executions on Linux where a parent process whose path ends with /node spawns a /bun process running a command line that includes bun_environment.js. It also matches related behavior where the command line shows downloading and installing Bun using curl from bun.sh, followed by shell sourcing/reload activity. This matters because supply-chain malware may use Bun to execute a staged JavaScript payload, and the rule relies on process creation telemetry including parent image, child image, and full command-line content.

Related detections9 linkedT1195.002 — drag to rearrange
Windows Process Creation: Bun executes bun_environment.js via node.exe
Suspicious Child Process Spawned by Python Interpreter via Process Creation
Suspicious npm Postinstall Node Execution From Fixtures Path (BeaverTail OtterCookie)
Suspicious TrueConf Update Chain Spawning Temporary Executable in Operation TrueChaos
Malicious TeamPCP durabletask Payload python3 managed.pyz from tmp (via process_creation)
Malicious PowerShell Download from bullethost.cloud Staging Server
Suspicious NPM Install Hook Executing Setup Script via Node
Suspicious Shai-Hulud Worm Stager Execution from Temp (via process_creation)
Suspicious Double Base64 Decoded Payload Piped to Shell in CI (reviewdog Supply Chain)
Linux Bun Runtime Execution: bun_environment.js via node-parent process
Pivot detection · T1195.002 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.