Malicious code in @flex-ng/error-component (npm)
The @flex-ng/error-component npm package is a malicious package published as part of a dependency confusion attack. It contains a preinstall hook that executes automatically during npm install, sending the installer's public IP and host telemetry to an attacker-controlled Sentry endpoint without user consent. This behavior is designed for reconnaissance to identify organizations that mistakenly install the malicious package instead of the intended private dependency. The package version 2.1.0 is affected. Removal alone may not fully remediate the compromise as the attacker may have gained broader access.
AI Analysis
Technical Summary
The @flex-ng/error-component package published by user 'click2ai' on npm impersonates an internal package to exploit misconfigured dependency resolvers. It declares a preinstall hook that installs @sentry/node and runs a script which initializes a Sentry client with a hardcoded attacker-controlled DSN. The script collects the installer's public IP via Cloudflare's trace endpoint and captures runtime environment details including hostname and OS username by triggering a deliberate error. This data is sent to the attacker's Sentry project, enabling attribution of successful installs to specific organizations. The malicious payload is identical across packages published by this user, differing only in package name and Sentry project ID. The exported init() API also silently relays exceptions and PII to the attacker if called without explicit configuration. The affected version is 2.1.0.
Potential Impact
Systems that install this package version are subject to unauthorized telemetry exfiltration, including public IP address, hostname, OS username, and runtime metadata, sent to an attacker-controlled Sentry project. This can lead to organizational reconnaissance and potential targeted follow-up attacks. The presence of this package indicates a likely compromise of the development environment or build pipeline. According to external sources, any computer with this package installed should be considered fully compromised, and all secrets and keys on that system should be rotated from a different, trusted machine.
Mitigation Recommendations
No official patch or fix is currently available. The package should be immediately removed from all environments. All secrets and credentials stored on affected systems must be rotated from a separate, uncompromised device. Review and correct dependency resolution configurations to prevent dependency confusion attacks, ensuring private packages are resolved correctly and not overridden by public packages with similar names. Monitor for and block installation of similarly named malicious packages. Since full system compromise is possible, consider rebuilding affected systems from known good backups.
Malicious code in @flex-ng/error-component (npm)
Description
The @flex-ng/error-component npm package is a malicious package published as part of a dependency confusion attack. It contains a preinstall hook that executes automatically during npm install, sending the installer's public IP and host telemetry to an attacker-controlled Sentry endpoint without user consent. This behavior is designed for reconnaissance to identify organizations that mistakenly install the malicious package instead of the intended private dependency. The package version 2.1.0 is affected. Removal alone may not fully remediate the compromise as the attacker may have gained broader access.
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 @flex-ng/error-component package published by user 'click2ai' on npm impersonates an internal package to exploit misconfigured dependency resolvers. It declares a preinstall hook that installs @sentry/node and runs a script which initializes a Sentry client with a hardcoded attacker-controlled DSN. The script collects the installer's public IP via Cloudflare's trace endpoint and captures runtime environment details including hostname and OS username by triggering a deliberate error. This data is sent to the attacker's Sentry project, enabling attribution of successful installs to specific organizations. The malicious payload is identical across packages published by this user, differing only in package name and Sentry project ID. The exported init() API also silently relays exceptions and PII to the attacker if called without explicit configuration. The affected version is 2.1.0.
Potential Impact
Systems that install this package version are subject to unauthorized telemetry exfiltration, including public IP address, hostname, OS username, and runtime metadata, sent to an attacker-controlled Sentry project. This can lead to organizational reconnaissance and potential targeted follow-up attacks. The presence of this package indicates a likely compromise of the development environment or build pipeline. According to external sources, any computer with this package installed should be considered fully compromised, and all secrets and keys on that system should be rotated from a different, trusted machine.
Mitigation Recommendations
No official patch or fix is currently available. The package should be immediately removed from all environments. All secrets and credentials stored on affected systems must be rotated from a separate, uncompromised device. Review and correct dependency resolution configurations to prevent dependency confusion attacks, ensuring private packages are resolved correctly and not overridden by public packages with similar names. Monitor for and block installation of similarly named malicious packages. Since full system compromise is possible, consider rebuilding affected systems from known good backups.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10221
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-pw64-8rr7-9h66"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff7768715ace432f2632
Added to database: 07/14/2026, 09:20:55 UTC
Last enriched: 07/14/2026, 09:39:32 UTC
Last updated: 07/28/2026, 17:03:52 UTC
Views: 10
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.