Malicious code in @finxsecdemo/utils (npm)
The npm package '@finxsecdemo/utils' versions 1.0.2 and 1.0.3 contain malicious code that executes during installation. The postinstall.js script performs an HTTPS GET request and DNS resolution to a hardcoded external domain, sending system information such as hostname, user info, and environment variables. This behavior effectively leaks the installer's source IP and DNS resolver IP to an attacker-controlled server. Additionally, the package's main function returns corrupted output that can disrupt consumers displaying formatted currency. This malicious activity occurs regardless of the package's labeling as a 'dependency confusion PoC.'
AI Analysis
Technical Summary
The '@finxsecdemo/utils' npm package versions 1.0.2 and 1.0.3 include a postinstall.js lifecycle script that unconditionally contacts a hardcoded OAST domain on every installation. It collects and transmits system information including os.hostname(), os.userInfo(), and process.env to the attacker's server, leaking the installer's IP and DNS resolver IP. The package's main export returns a string that corrupts formatted currency output, impacting any dependent software that uses it. The network callback and output corruption happen regardless of the package's console message claiming it is a 'dependency confusion PoC.' The OpenSSF Package Analysis project has identified this package as malicious due to its communication with a domain associated with malicious activity.
Potential Impact
This malicious package leaks sensitive system information and network details to an attacker-controlled domain during installation, potentially exposing the installer's environment and network topology. It also corrupts output in dependent applications that display formatted currency, which may cause functional or data integrity issues. There is no indication of active exploitation in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing versions 1.0.2 and 1.0.3 of '@finxsecdemo/utils'. If these versions are present, remove the package and replace it with a trusted alternative. Monitor for updates from the package maintainer or npm registry for any official fixes or advisories. Since this is not a cloud service, remediation depends on user action.
Malicious code in @finxsecdemo/utils (npm)
Description
The npm package '@finxsecdemo/utils' versions 1.0.2 and 1.0.3 contain malicious code that executes during installation. The postinstall.js script performs an HTTPS GET request and DNS resolution to a hardcoded external domain, sending system information such as hostname, user info, and environment variables. This behavior effectively leaks the installer's source IP and DNS resolver IP to an attacker-controlled server. Additionally, the package's main function returns corrupted output that can disrupt consumers displaying formatted currency. This malicious activity occurs regardless of the package's labeling as a 'dependency confusion PoC.'
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 '@finxsecdemo/utils' npm package versions 1.0.2 and 1.0.3 include a postinstall.js lifecycle script that unconditionally contacts a hardcoded OAST domain on every installation. It collects and transmits system information including os.hostname(), os.userInfo(), and process.env to the attacker's server, leaking the installer's IP and DNS resolver IP. The package's main export returns a string that corrupts formatted currency output, impacting any dependent software that uses it. The network callback and output corruption happen regardless of the package's console message claiming it is a 'dependency confusion PoC.' The OpenSSF Package Analysis project has identified this package as malicious due to its communication with a domain associated with malicious activity.
Potential Impact
This malicious package leaks sensitive system information and network details to an attacker-controlled domain during installation, potentially exposing the installer's environment and network topology. It also corrupts output in dependent applications that display formatted currency, which may cause functional or data integrity issues. There is no indication of active exploitation in the wild at this time.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing versions 1.0.2 and 1.0.3 of '@finxsecdemo/utils'. If these versions are present, remove the package and replace it with a trusted alternative. Monitor for updates from the package maintainer or npm registry for any official fixes or advisories. Since this is not a cloud service, remediation depends on user action.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-11170
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7ff60abf8831d53988202c
Added to database: 08/15/2026, 05:15:54 UTC
Last enriched: 08/15/2026, 05:26:43 UTC
Last updated: 08/15/2026, 05:38:34 UTC
Views: 4
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.