Which versions of biklirouter are malicious?

The following npm versions of biklirouter are flagged malicious: 0.5.46, 0.5.47. Treat any of these as compromised.

How do I remediate biklirouter if I installed it?

biklirouter 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 biklirouter — how do I know if it already compromised me?

If biklirouter 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 biklirouter part of a known attack campaign?

Yes — biklirouter is associated with the GHSA-f5c6-4rpr-wjhp, IN-MAL-2026-017464, IN-MAL-2026-017466 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 biklirouter 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 biklirouter (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging biklirouter across your stack and pipelines.

Malicious package

biklirouternpm

biklirouter is a confirmed malicious npm package (MAL-2026-13787) that steals credentials and exfiltrates sensitive data (malicious versions 0.5.46, 0.5.47). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in biklirouter (npm)

MAL-2026-13787

Immediate action

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

npm uninstall biklirouter

What this malware does

Package ships a compiled Next.js application (server routes under app/.next-cli-build/server/app/api/) implementing an LLM/AI-provider router: OAuth import flows for provider CLIs (codex, cursor, cline, kilo, droid, hermes, jcode, deepseek, opencode, openclaw, grok, devin, cowork), OpenAI-compatible endpoints (/api/v1/chat/completions, /embeddings, /images/generations, /videos/*, /responses, /messages), provider validation/testing (ping, curl), and Tailscale tunnel management. Many API route bundles include child_process, os, http/https, and process.env because Next.js server bundling co-locates these Node built-ins per route file; static keyword co-occurrence of require('child_process') + POST + process.env in minified route bundles matches the exfiltration pattern shape but reflects normal Next.js server-side rendering plus the app's documented purpose (spawn CLI tools, validate providers via ping, test provider endpoints). cli.js performs a version check against https://registry.npmjs.org (the official npm registry) and reads os.homedir() for local config. No traced code path shows installer-secret paths (~/.aws, ~/.ssh, ~/.npmrc contents) being read and sent to an author-controlled host; no lifecycle scripts fetch-and-exec remote content; no hardcoded non-registry C2 destination is confirmed in the evidence. The behavior surface (spawning CLIs, reading provider credentials that the user configures into the app, contacting external LLM providers) is consistent with the app's declared router purpose, but the density of shell-exec + network primitives across dozens of route handlers plus a MITM server module (app/src/mitm/server.js) warrants human review of the maintainer and endpoints before trust.

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

2 flagged

0.5.460.5.47

Indicators of compromise (SHA-256)

22940b637d3ee937dbb5f7ab3c9caa4a9509ea1d22eff921706dbbf5915dd847

aa35b0b8fe046a8dd43a4307742214223c3f908b5ba65fa6d24dae18b33cff9b

bc79835ed6721e5aa390905e44a7419d1f65fa36918827412824b6b171e211fc

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 biklirouter (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging biklirouter across your stack and pipelines.
If you installed it — respond
biklirouter 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 biklirouter 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 biklirouter 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. biklirouter on npm has been identified as a malicious package (versions 0.5.46, 0.5.47 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f5c6-4rpr-wjhpIN-MAL-2026-017464IN-MAL-2026-017466

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks biklirouter-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