Malicious code in enbd-react-logger (npm)
The enbd-react-logger npm package version 4.0.0 is a malicious package published as part of a dependency confusion attack targeting organizations using an internal 'enbd' namespace. It contains a preinstall script that executes automatically during npm install, sending the host's public IP address, hostname, OS username, and runtime metadata to an attacker-controlled Sentry project without user consent. This behavior enables reconnaissance by the attacker to identify successful installs and affected organizations. The package also hardcodes the attacker's Sentry DSN, causing any downstream error reporting to leak data to the attacker. Removal of the package alone may not fully remediate the compromise, as the attacker may have gained broader control of the system.
AI Analysis
Technical Summary
The enbd-react-logger package (version 4.0.0) was published to the npm registry by an attacker impersonating an internal package namespace used by Emirates NBD. It includes a preinstall hook that runs automatically on npm install, executing a script that initializes the @sentry/node client with a hardcoded attacker-owned Sentry DSN and sendDefaultPii enabled. This script collects the installing host's public egress IP by querying Cloudflare's trace endpoint and deliberately triggers a runtime exception to send telemetry data including public IP, hostname, OS username, and environment metadata to the attacker's Sentry project. This enables the attacker to perform reconnaissance on victims who mistakenly install this public package due to misconfigured dependency resolution. The attack is part of a broader campaign using similar packages targeting different internal namespaces, each beaconing to distinct Sentry project IDs. The package's malicious behavior is embedded in the install-time payload and the source code, making it a severe threat. The package version affected is exactly 4.0.0. No official patch or remediation is provided by the vendor, and the package should be considered fully malicious.
Potential Impact
Installation of this package results in unauthorized exfiltration of sensitive host telemetry and personally identifiable information (PII) including public IP address, hostname, OS username, and runtime environment metadata to an attacker-controlled Sentry project. This compromises confidentiality and privacy of the affected system. The attacker can identify which organizations have installed the package, enabling targeted follow-up attacks. The presence of the malicious preinstall script means that the compromise occurs before application code runs, increasing risk. According to external malware analysis, any system with this package installed or running should be considered fully compromised, and all secrets and keys on that system should be rotated from a different, trusted machine. Removal of the package alone does not guarantee full remediation.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove the enbd-react-logger package version 4.0.0 from all affected systems. Because the package executes code at install time and exfiltrates sensitive data, assume full system compromise upon installation. Rotate all secrets, credentials, and keys that were stored or accessible on the affected systems, performing this rotation from a separate, trusted environment. Review and correct any misconfigured dependency resolution to prevent accidental installation of public packages mimicking internal namespaces. Monitor for any further suspicious activity related to this package or similar dependency confusion attacks. There is no vendor advisory indicating any official fix or that no action is required.
Malicious code in enbd-react-logger (npm)
Description
The enbd-react-logger npm package version 4.0.0 is a malicious package published as part of a dependency confusion attack targeting organizations using an internal 'enbd' namespace. It contains a preinstall script that executes automatically during npm install, sending the host's public IP address, hostname, OS username, and runtime metadata to an attacker-controlled Sentry project without user consent. This behavior enables reconnaissance by the attacker to identify successful installs and affected organizations. The package also hardcodes the attacker's Sentry DSN, causing any downstream error reporting to leak data to the attacker. Removal of the package alone may not fully remediate the compromise, as the attacker may have gained broader control of the system.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The enbd-react-logger package (version 4.0.0) was published to the npm registry by an attacker impersonating an internal package namespace used by Emirates NBD. It includes a preinstall hook that runs automatically on npm install, executing a script that initializes the @sentry/node client with a hardcoded attacker-owned Sentry DSN and sendDefaultPii enabled. This script collects the installing host's public egress IP by querying Cloudflare's trace endpoint and deliberately triggers a runtime exception to send telemetry data including public IP, hostname, OS username, and environment metadata to the attacker's Sentry project. This enables the attacker to perform reconnaissance on victims who mistakenly install this public package due to misconfigured dependency resolution. The attack is part of a broader campaign using similar packages targeting different internal namespaces, each beaconing to distinct Sentry project IDs. The package's malicious behavior is embedded in the install-time payload and the source code, making it a severe threat. The package version affected is exactly 4.0.0. No official patch or remediation is provided by the vendor, and the package should be considered fully malicious.
Potential Impact
Installation of this package results in unauthorized exfiltration of sensitive host telemetry and personally identifiable information (PII) including public IP address, hostname, OS username, and runtime environment metadata to an attacker-controlled Sentry project. This compromises confidentiality and privacy of the affected system. The attacker can identify which organizations have installed the package, enabling targeted follow-up attacks. The presence of the malicious preinstall script means that the compromise occurs before application code runs, increasing risk. According to external malware analysis, any system with this package installed or running should be considered fully compromised, and all secrets and keys on that system should be rotated from a different, trusted machine. Removal of the package alone does not guarantee full remediation.
Mitigation Recommendations
No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove the enbd-react-logger package version 4.0.0 from all affected systems. Because the package executes code at install time and exfiltrates sensitive data, assume full system compromise upon installation. Rotate all secrets, credentials, and keys that were stored or accessible on the affected systems, performing this rotation from a separate, trusted environment. Review and correct any misconfigured dependency resolution to prevent accidental installation of public packages mimicking internal namespaces. Monitor for any further suspicious activity related to this package or similar dependency confusion attacks. There is no vendor advisory indicating any official fix or that no action is required.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10231
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-96hr-p56w-4x2m"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff7168715ace432f2313
Added to database: 07/14/2026, 09:20:49 UTC
Last enriched: 07/14/2026, 09:37:52 UTC
Last updated: 07/31/2026, 05:59:55 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.