# MAL-2026-11093: Malicious code in @heartlandone-private/fontawesome-pro (npm)


- **Type:** Malicious package
- **Package:** `@heartlandone-private/fontawesome-pro` (npm)
- **Published:** 27 Jul 2026

## What is MAL-2026-11093?

MAL-2026-11093 is a malicious package in @heartlandone-private/fontawesome-pro, published on 27 Jul 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-11093?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-11093 is a malicious package: @heartlandone-private/fontawesome-pro (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-11093/ (Markdown: https://insights.sbomify.com/MAL-2026-11093/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-11093

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-11093/
Summaries are generated and may contain mistakes; the official description above is the record.