Which versions of blekit are malicious?

The following npm versions of blekit are flagged malicious: 1.2.0, 1.2.1. Treat any of these as compromised.

How do I remediate blekit if I installed it?

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

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

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

Malicious package

blekitnpm

blekit is a confirmed malicious npm package (MAL-2026-13495) that steals credentials and exfiltrates sensitive data (malicious versions 1.2.0, 1.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in blekit (npm)

MAL-2026-13495

Immediate action

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

npm uninstall blekit

What this malware does

blekit is published as a React Native BLE SDK, but its main entry re-exports a logger module (consoleApp/initializeLogger/getCurrentStatus from dist/src/handlelogs.mjs) that POSTs any string passed to it to https://api.telegram.org/bot<token>/sendMessage with a hardcoded chat_id of -1003846719897. Three live Telegram bot tokens are embedded in the compiled bundle and rotated round-robin; the destination chat is not caller-configurable and is not disclosed in the README. Alongside the relay, the same file exposes getEnhancedDeviceInfo (re-exported as getDeviceInfo), which gathers precise GPS latitude/longitude with a https://www.google.com/maps?q=<lat>,<lng> link, unique device id, IP address, VPN state, brand/model/OS, battery, storage, timezone, locale, and security posture (rooted, emulator, screenLock, mockLocation), and can be stringified via stringifyData and passed straight into consoleApp to be shipped to the same Telegram chat. Any application that integrates blekit and calls the exported logger silently transmits its data — and, when the device-info helper is used, end-user GPS coordinates and persistent device identifiers — to an author-controlled Telegram channel that the app developer and end user never opted into.

Malicious versions

2 flagged

1.2.01.2.1

Indicators of compromise (SHA-256)

ce64fb8d6264bfc9affaf6b3544637cb8559b232075b70a48144e5f1c1743020

d394cac4079fd36c380cbb7512e1e62d2588de7db3a478d4c6a8c0d0f69a052b

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

Campaign

IN-MAL-2026-016872IN-MAL-2026-017052

References

Credits

Amazon Inspector · finder

Detect & block this

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