Which versions of iot-kfh-s3 are malicious?

The following npm versions of iot-kfh-s3 are flagged malicious: 17.3.23. Treat any of these as compromised.

How do I remediate iot-kfh-s3 if I installed it?

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.

I already installed iot-kfh-s3 — how do I know if it already compromised me?

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

Yes — iot-kfh-s3 is associated with the GHSA-qg52-c79f-3q5c, IN-MAL-2026-011318 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 iot-kfh-s3 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 iot-kfh-s3 (version 17.3.23). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging iot-kfh-s3 across your stack and pipelines.

Malicious package

iot-kfh-s3npm

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)

MAL-2026-10921

Immediate action

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

npm uninstall iot-kfh-s3

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

1 flagged

17.3.23

Indicators of compromise (SHA-256)

d951dbac36ed1916b5dbff7333d074898752088132c2ec6e2b12fe223b835393

1c402827c1e00592a8936a9304c2cccc45189126fc447038f67350a8a9124c81

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for iot-kfh-s3 (version 17.3.23). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging iot-kfh-s3 across your stack and pipelines.
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 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 iot-kfh-s3 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. iot-kfh-s3 on npm has been identified as a malicious package (version 17.3.23 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qg52-c79f-3q5cIN-MAL-2026-011318

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database