# MAL-2026-3771: Malicious code in request-logger-canary (npm)


- **Type:** Malicious package
- **Package:** `request-logger-canary` (npm)
- **Published:** 14 May 2026
- **Also known as:** GHSA-hvf9-xwj5-pqqj

## What is MAL-2026-3771?

MAL-2026-3771 is a malicious package in request-logger-canary, published on 14 May 2026. 

### Official description

request-logger-canary@1.0.0 ships a preinstall.js that, when `npm install` runs, opens a TCP socket to 52.74.242.200:8851 and pipes an interactive `/bin/sh` to the remote endpoint (stdin/stdout/stderr all bridged to the socket). The code executes unconditionally at install time via scripts.preinstall — there is no guard, no `if (false)`, no environment check. The README falsely claims the reverse shell is dead code wrapped in `if (false)` and located in postinstall.js; the live payload is actually in preinstall.js with no guard. This misdirection is itself evidence of deliberate supply-chain attack intent. Any machine running `npm install request-logger-canary` hands a root-of-user interactive shell to the operator of 52.74.242.200.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

## What should I do about MAL-2026-3771?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-3771 is a malicious package: request-logger-canary (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-3771/ (Markdown: https://insights.sbomify.com/MAL-2026-3771/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-3771

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-3771/
Summaries are generated and may contain mistakes; the official description above is the record.