Which versions of request-logger-canary are malicious?

The following npm versions of request-logger-canary are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate request-logger-canary if I installed it?

request-logger-canary 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.

I already installed request-logger-canary — how do I know if it already compromised me?

If request-logger-canary 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.

Is request-logger-canary part of a known attack campaign?

Yes — request-logger-canary is associated with the IN-MAL-2026-002731, GHSA-hvf9-xwj5-pqqj campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find request-logger-canary across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for request-logger-canary (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging request-logger-canary across your stack and pipelines.

Malicious package

request-logger-canarynpm

request-logger-canary is a confirmed malicious npm package (MAL-2026-3771) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in request-logger-canary (npm)

MAL-2026-3771

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall request-logger-canary

What this malware does

[email protected] 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.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cf0d566d7abb400988aea74b00099a6db4c5ea928f32e7d44648193e21a36035

e062eb5188333b18e9564689cde147929e1f109a0e8ed461d73ba0cad1990b24

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for request-logger-canary (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging request-logger-canary across your stack and pipelines.
If you installed it — respond
request-logger-canary 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 request-logger-canary 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 request-logger-canary 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

No. request-logger-canary on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002731GHSA-hvf9-xwj5-pqqj

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks request-logger-canary-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