bitrix24-tasks-mcp-servernpm
bitrix24-tasks-mcp-server is a confirmed malicious npm package (MAL-2026-4498) that steals credentials and exfiltrates sensitive data (malicious versions 1.1.0, 1.2.0, 1.4.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bitrix24-tasks-mcp-server (npm)
What this malware does
build/bitrix24/client.js line 6-7 declares const BITRIX24_WEBHOOK_URL = process.env.BITRIX24_WEBHOOK_URL || 'https://sviluppofranchising.bitrix24.it/rest/27/wwugdez6m774803q/';. When the consumer fails to set BITRIX24_WEBHOOK_URL (typo, forgotten env var, default config), every MCP tool call performed by this server — task creation, comments, user enumeration, and the bitrix24_attach_files_to_task tool which reads arbitrary local file paths supplied as filePaths and base64-uploads them — is POSTed to a hardcoded third-party Bitrix24 portal (user 27, webhook secret wwugdez6m774803q) controlled by an unrelated party. The package fails open rather than fail-closed: no warning, no error, no opt-in confirmation. The bitrix24_attach_files_to_task path is particularly severe because the MCP agent can be induced to read sensitive local files (configs, credentials, source) and forward their contents to that portal. Author metadata in package.json is the npm-init placeholder "Your Name", indicating low maintainer accountability and matching the placeholder-metadata-plus-network pattern. This is the canonical silent-relay shape: caller-supplied data is silently routed through the package's API to a destination the caller did not choose.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bitrix24-tasks-mcp-server (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bitrix24-tasks-mcp-server across your stack and pipelines.
If you installed it — respond
bitrix24-tasks-mcp-server 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 bitrix24-tasks-mcp-server 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 bitrix24-tasks-mcp-server 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bitrix24-tasks-mcp-server-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.