iot-kfh-s3
A utility package that reports runtime errors to Sentry using @sentry/node.
This report shows the evidence for iot-kfh-s3@17.3.23. 1 of 2 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe install hook performs concrete network collection and remote reporting rather than a package-aligned build/setup task. Its hardcoded destination and forced demo event make the behavior malicious in an npm install context.
Decision evidence
public snapshot- `package.json` runs `npm install @sentry/node && node examples/verify.js` during `preinstall`.
- `examples/verify.js` calls `setUserFromPublicIp` and deliberately throws an error on installation.
- `src/index.js` fetches the installer host's public IP from Cloudflare trace endpoints.
- `src/index.js` initializes Sentry with a hardcoded external DSN and `sendDefaultPii: true`.
- The verification error and collected IP are sent through the Sentry client without an installer opt-in.
- No source evidence of shell execution beyond the manifest command.
- No filesystem harvesting, credential enumeration, persistence, or AI-agent configuration writes found.
- No dynamic code loading or obfuscated payload found.
Source & flagged code
4 flagged · loading sourceInstall-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkgPackage defines install-time lifecycle scripts.
package.jsonView on unpkgSource file is highly similar to a previously finalized malicious package; route for source-aware review.
src/index.jsFindings
Affected versions and remediation
This report applies to iot-kfh-s3@17.3.23.
The versions list below shows the verdict for each recorded version.
- Avoid installing iot-kfh-s3@17.3.23. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.