blekitnpm
Advisory published Updated
blekit is a confirmed malicious npm package (MAL-2026-13495) that executes malicious code on install (malicious versions 0.1.0, 0.2.0, 0.3.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in blekit (npm)
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.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for blekit (9 malicious versions).
If you installed it — respond
Remove blekit from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If blekit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
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 malicious outbound activity and severs the channel.