NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

git-en-boite-loggingnpm

Advisory published Updated

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)

MAL-2026-17214
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall git-en-boite-logging

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

1 flagged
0.0.0

Indicators of compromise (SHA-256)

f6ebee9f4428d7f14f6f941438064715c8bece34c5fe6bfedf32bbd8cba226c0

Detection & response playbook

Backdoor / remote access

  1. Find it

    Search your lockfiles and build artifacts for git-en-boite-logging (version 0.0.0).

  2. 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.

  3. Did it already run?

    If git-en-boite-logging was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. git-en-boite-logging on npm has been identified as a malicious package (version 0.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020579

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
git-en-boite-logging (npm) malicious package — MAL-2026-17214 | O3 Security