Which versions of @mrbenty8jf1p9y5/oidc-bind-canary are malicious?

The following npm versions of @mrbenty8jf1p9y5/oidc-bind-canary are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate @mrbenty8jf1p9y5/oidc-bind-canary if I installed it?

@mrbenty8jf1p9y5/oidc-bind-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 @mrbenty8jf1p9y5/oidc-bind-canary — how do I know if it already compromised me?

If @mrbenty8jf1p9y5/oidc-bind-canary 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.

Is @mrbenty8jf1p9y5/oidc-bind-canary part of a known attack campaign?

Yes — @mrbenty8jf1p9y5/oidc-bind-canary is associated with the IN-MAL-2026-017133 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 @mrbenty8jf1p9y5/oidc-bind-canary across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @mrbenty8jf1p9y5/oidc-bind-canary (version 0.0.3).

Malicious package

@mrbenty8jf1p9y5/oidc-bind-canarynpm

Advisory published Aug 7, 2026Updated Aug 7, 2026

@mrbenty8jf1p9y5/oidc-bind-canary is a confirmed malicious npm package (MAL-2026-13626) that opens a backdoor for remote access (malicious version 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mrbenty8jf1p9y5/oidc-bind-canary (npm)

MAL-2026-13626

Immediate action

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

npm uninstall @mrbenty8jf1p9y5/oidc-bind-canary

What this malware does

The package's postinstall lifecycle script issues an HTTPS request from the installer's machine to a Cloudflare tunnel at wiki-shared-carlos-exempt.trycloudflare.com on path /token-capture. The request is sent with the Host header spoofed to dependabot-api.githubapp.com and with TLS certificate validation disabled (rejectUnauthorized:false), disguising the callout as legitimate GitHub Dependabot traffic. The destination path name (/token-capture) and the disguise mechanics indicate an install-time beacon to an attacker-controlled listener, firing automatically on npm install.

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

1a9ed4acf296e53ad5955f759a0f0692d641781b1bd4e67ada1c116216f96fc3

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @mrbenty8jf1p9y5/oidc-bind-canary (version 0.0.3).
If you installed it — respond
@mrbenty8jf1p9y5/oidc-bind-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 @mrbenty8jf1p9y5/oidc-bind-canary 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. @mrbenty8jf1p9y5/oidc-bind-canary on npm has been identified as a malicious package (version 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017133

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @mrbenty8jf1p9y5/oidc-bind-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