enbd-react-logger
A utility package that reports runtime errors to Sentry using @sentry/node.
This report shows the evidence for enbd-react-logger@4.0.0. 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 4mo ago · by lpm-firewall-aiSource inspection confirms unconsented install-time network telemetry to a hardcoded Sentry project plus public IP collection. Although the package exposes a plausible logging API, executing that reporting path in preinstall is concrete malicious install-hook abuse.
Decision evidence
public snapshot- package.json preinstall runs npm install @sentry/node && node examples/verify.js during consumer install
- examples/verify.js calls init() with no DSN, so src/index.js falls back to a hardcoded Sentry DSN
- examples/verify.js calls setUserFromPublicIp with Cloudflare trace URL during preinstall
- examples/verify.js intentionally triggers an exception via check() and flushes Sentry events during preinstall
- src/index.js defaults sendDefaultPii: true and reports captured exceptions to Sentry
- No child_process beyond declared lifecycle command, eval/vm/Function, native/binary loading, persistence, destructive writes, or AI-agent control-surface writes found
- Runtime logging API is package-aligned when explicitly used by an application
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 enbd-react-logger@4.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing enbd-react-logger@4.0.0. 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.