Which versions of bt2-api-gateway-node-js are malicious?

The following npm versions of bt2-api-gateway-node-js are flagged malicious: 999.0.0, 999.0.1. Treat any of these as compromised.

How do I remediate bt2-api-gateway-node-js if I installed it?

bt2-api-gateway-node-js 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 bt2-api-gateway-node-js — how do I know if it already compromised me?

If bt2-api-gateway-node-js 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 bt2-api-gateway-node-js part of a known attack campaign?

Yes — bt2-api-gateway-node-js is associated with the IN-MAL-2026-019324, IN-MAL-2026-019326 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 bt2-api-gateway-node-js 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 bt2-api-gateway-node-js (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bt2-api-gateway-node-js across your stack and pipelines.

Malicious package

bt2-api-gateway-node-jsnpm

bt2-api-gateway-node-js is a confirmed malicious npm package (MAL-2026-15813) that steals credentials and exfiltrates sensitive data (malicious versions 999.0.0, 999.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bt2-api-gateway-node-js (npm)

MAL-2026-15813

Immediate action

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

npm uninstall bt2-api-gateway-node-js

What this malware does

[email protected] runs a postinstall-triggered IIFE in index.js that reads installer-owned secrets from disk — ~/.ssh private keys, ~/.aws/{credentials,config,sso/cache}, ~/.azure, gcloud ADC, ~/.kube/config, ~/.docker/config.json, gh hosts.yml, ~/.netrc, ~/.npmrc, ~/.pypirc, ~/.gem/credentials, ~/.cargo/credentials, ~/.pgpass, ~/.my.cnf, and vercel/netlify/supabase/firebase tokens — and sweeps process.env for TOKEN/KEY/SECRET/PASSWORD and AWS/AZURE/GITHUB/STRIPE variables. The collected data is JSON-serialized, base64-encoded, and POSTed to two hardcoded destinations: the Telegram Bot API (api.telegram.org/bot<token>/sendMessage) and http://2.26.82.63:8888/collect over plain HTTP. Execution aborts if NODE_ENV=test, CI=true, JEST_WORKER_ID or VITEST is set, or /.dockerenv exists, and is delayed by a randomized 5–15 second setTimeout to evade CI and sandbox observation. The version number (999.0.1) and package name are consistent with a dependency-confusion lure targeting an internal 'bt2-api-gateway' package.

The OpenSSF Package Analysis project identified 'bt2-api-gateway-node-js' @ 999.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

999.0.0999.0.1

Indicators of compromise (SHA-256)

1e7b3146f31802aabbf0fcf530d3581e85274664be041a9c7ef12dfb3eb1713b

dc93cb460e7ec59d420f549dbd0180b89198e4c14228cc6f71b9ee2826a737cd

e3a3256b290402643d8dc39967ec2724fdbc490105a0581a1e3c1b2d96faee3e

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

Campaign

IN-MAL-2026-019324IN-MAL-2026-019326

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks bt2-api-gateway-node-js-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