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 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @mrbenty8jf1p9y5/oidc-bind-canary — how do I know if it already compromised me?

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

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

Malicious package

@mrbenty8jf1p9y5/oidc-bind-canarynpm

@mrbenty8jf1p9y5/oidc-bind-canary is a confirmed malicious npm package (MAL-2026-13626) that steals credentials and exfiltrates sensitive data (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

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @mrbenty8jf1p9y5/oidc-bind-canary (version 0.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @mrbenty8jf1p9y5/oidc-bind-canary across your stack and pipelines.
If you installed it — respond
@mrbenty8jf1p9y5/oidc-bind-canary is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @mrbenty8jf1p9y5/oidc-bind-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 @mrbenty8jf1p9y5/oidc-bind-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. @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 credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database