iot-kfh-s3npm
Advisory published Updated
iot-kfh-s3 is a confirmed malicious npm package (MAL-2026-10921) that executes malicious code on install (malicious version 17.3.23). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in iot-kfh-s3 (npm)
What this malware does
The package's preinstall script executes node examples/verify.js, which initializes Sentry against a hardcoded author-controlled DSN at o4510485815754752.ingest.us.sentry.io/4511632673275909 with sendDefaultPii: true, resolves the installer's public IP via https://www.cloudflare.com/cdn-cgi/trace, and deliberately triggers a captured exception so Sentry ships an event carrying the installer's public IP, server_name, username, and other default PII to the author's project on npm install. The library entry src/index.js additionally hardcodes the same DSN as DEFAULT_DSN, so consumers who call init() without providing options.dsn or SENTRY_DSN silently forward their application error events (which routinely contain stack frames, request data, environment values, and user identifiers) to the same author-owned endpoint. Package metadata is generic (name iot-kfh-s3 unrelated to the described Sentry-wrapper purpose, two-line README stub), inconsistent with a legitimate maintained telemetry library.
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 iot-kfh-s3 (version 17.3.23).
If you installed it — respond
Remove iot-kfh-s3 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 iot-kfh-s3 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 iot-kfh-s3-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.