git-en-boite-loggingnpm
git-en-boite-logging is a confirmed malicious npm package (MAL-2026-17214) that opens a backdoor for remote access (malicious version 0.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in git-en-boite-logging (npm)
What this malware does
package.json declares a preinstall lifecycle hook that runs wget to a hardcoded webhook.site collector URL (https://webhook.site/3fcfa5af-1b4e-4556-9d48-26190d02795f/), passing $(whoami), $(hostname), and $(pwd) as query parameters. On npm install, npm invokes the preinstall script automatically, so the installer's OS username, host name, and current working directory are transmitted to an anonymous third-party webhook collector without any user action. This is the canonical dependency-confusion / reconnaissance beacon shape: an otherwise-empty package whose only on-install effect is to phone home installer identity to an attacker-chosen endpoint, typically used to confirm ingress into a target's internal build environment before staging a follow-on payload.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for git-en-boite-logging (version 0.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging git-en-boite-logging across your stack and pipelines.
If you installed it — respond
git-en-boite-logging establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If git-en-boite-logging was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks git-en-boite-logging before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks git-en-boite-logging-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.