Malicious code in @heartlandone-private/fontawesome-pro (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5dc8f9f53c05ecc2642ce82c3841e046025662c206f002b4c6da11ff0cbc763d) The package's postinstall lifecycle hook runs `node index.js`, which issues an HTTPS GET to a hardcoded Burp Collaborator subdomain at `e0fumpwx24ddfmenzmg0izs2atgk4es3.oastify.com/dependency-confusion` with a User-Agent identifying it as a dependency-confusion probe. On any `npm install` that resolves this scoped name, the request fires automatically and discloses installer identity (source IP, DNS resolver, timing, request metadata) to a third-party out-of-band interaction server controlled by whoever provisioned the Collaborator instance. The package name uses a private-scope pattern (`@heartlandone-private/fontawesome-pro`) that mimics an internal artifact, consistent with a dependency-confusion attempt aimed at organizations whose internal `@heartlandone-private` scope is not reserved on the public registry. Whether the operator's intent is authorized red-team testing or opportunistic exploitation, any consumer whose install pipeline resolves this public package receives install-time code execution and outbound network signalling to an attacker-controlled callback. ## Source: ossf-package-analysis (b5bd52805195c9e3575760b3eaf605a2b9cb0fcbdde2311b7075d2d8095c4900) The OpenSSF Package Analysis project identified '@heartlandone-private/fontawesome-pro' @ 6.3.3 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.
AI Analysis
Technical Summary
The '@heartlandone-private/fontawesome-pro' npm package versions 6.3.3 and 6.3.6 include a postinstall script that runs index.js, which issues an HTTPS request to a Burp Collaborator subdomain at r7z7t23a9hkqmzl06zndpczfh6nxbszh.oastify.com. This request transmits identifying information about the installer, including outbound IP and DNS resolver details, to an attacker-controlled server. The package is published publicly under a private-looking scope, facilitating dependency confusion attacks. The package's sole behavior is this beaconing activity, which occurs without user consent or control.
Potential Impact
The malicious package leaks sensitive environment information such as the installer's IP address and DNS resolver to an attacker-controlled domain during installation. This can lead to reconnaissance by threat actors, potentially enabling further targeted attacks or exploitation. No direct code execution or system compromise beyond this information leakage is described.
Mitigation Recommendations
Users and organizations should avoid installing the '@heartlandone-private/fontawesome-pro' package versions 6.3.3 and 6.3.6 from public npm registries. There is no official patch or fix available. Review and restrict npm registry configurations to prevent resolution of private-scoped packages from public registries. Monitor dependency sources carefully to avoid dependency confusion attacks. Patch status is not yet confirmed — check vendor advisories or npm security notices for updates.
Malicious code in @heartlandone-private/fontawesome-pro (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5dc8f9f53c05ecc2642ce82c3841e046025662c206f002b4c6da11ff0cbc763d) The package's postinstall lifecycle hook runs `node index.js`, which issues an HTTPS GET to a hardcoded Burp Collaborator subdomain at `e0fumpwx24ddfmenzmg0izs2atgk4es3.oastify.com/dependency-confusion` with a User-Agent identifying it as a dependency-confusion probe. On any `npm install` that resolves this scoped name, the request fires automatically and discloses installer identity (source IP, DNS resolver, timing, request metadata) to a third-party out-of-band interaction server controlled by whoever provisioned the Collaborator instance. The package name uses a private-scope pattern (`@heartlandone-private/fontawesome-pro`) that mimics an internal artifact, consistent with a dependency-confusion attempt aimed at organizations whose internal `@heartlandone-private` scope is not reserved on the public registry. Whether the operator's intent is authorized red-team testing or opportunistic exploitation, any consumer whose install pipeline resolves this public package receives install-time code execution and outbound network signalling to an attacker-controlled callback. ## Source: ossf-package-analysis (b5bd52805195c9e3575760b3eaf605a2b9cb0fcbdde2311b7075d2d8095c4900) The OpenSSF Package Analysis project identified '@heartlandone-private/fontawesome-pro' @ 6.3.3 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.
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 '@heartlandone-private/fontawesome-pro' npm package versions 6.3.3 and 6.3.6 include a postinstall script that runs index.js, which issues an HTTPS request to a Burp Collaborator subdomain at r7z7t23a9hkqmzl06zndpczfh6nxbszh.oastify.com. This request transmits identifying information about the installer, including outbound IP and DNS resolver details, to an attacker-controlled server. The package is published publicly under a private-looking scope, facilitating dependency confusion attacks. The package's sole behavior is this beaconing activity, which occurs without user consent or control.
Potential Impact
The malicious package leaks sensitive environment information such as the installer's IP address and DNS resolver to an attacker-controlled domain during installation. This can lead to reconnaissance by threat actors, potentially enabling further targeted attacks or exploitation. No direct code execution or system compromise beyond this information leakage is described.
Mitigation Recommendations
Users and organizations should avoid installing the '@heartlandone-private/fontawesome-pro' package versions 6.3.3 and 6.3.6 from public npm registries. There is no official patch or fix available. Review and restrict npm registry configurations to prevent resolution of private-scoped packages from public registries. Monitor dependency sources carefully to avoid dependency confusion attacks. Patch status is not yet confirmed — check vendor advisories or npm security notices for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-11093
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735730bf8831d53913cef5
Added to database: 08/05/2026, 15:30:56 UTC
Last enriched: 08/05/2026, 15:42:47 UTC
Last updated: 09/07/2026, 22:03:35 UTC
Views: 21
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.