Which versions of font-hub are malicious?

The following npm versions of font-hub are flagged malicious: 1.5.2. Treat any of these as compromised.

How do I remediate font-hub if I installed it?

font-hub is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed font-hub — how do I know if it already compromised me?

If font-hub was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is font-hub part of a known attack campaign?

Yes — font-hub is associated with the IN-MAL-2026-010262 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find font-hub across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for font-hub (version 1.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging font-hub across your stack and pipelines.

Malicious package

font-hubnpm

font-hub is a confirmed malicious npm package (MAL-2026-10450) that steals credentials and exfiltrates sensitive data (malicious version 1.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in font-hub (npm)

MAL-2026-10450

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall font-hub

What this malware does

index.js exports a getPlugin() function that performs an HTTPS request to https://svganchordev.net/icons/<token> and passes the response's credits field into new Function('require','module','exports',...,'Promise', data.credits), then invokes it with the real require, process, Buffer, and I/O globals. This executes attacker-controlled JavaScript with full Node.js privileges whenever a consumer imports the package and calls its default export. The package presents itself as a React SVG/font helper, but the README content documents an unrelated 'polymarket-clob-api' project, and the declared dependencies (@primno/dpapi, better-sqlite3, node-machine-id) are consistent with browser-credential-store access on Windows. The fetched endpoint is unrelated to any font/SVG CDN; an iconDomain map referencing cloudflare/fastly/akamai and a font-awesome path are decorative and unused by the live code path, which unconditionally targets svganchordev.net.

Malicious versions

1 flagged

1.5.2

Indicators of compromise (SHA-256)

3df3dbd8669e4658a00a698bd8bd233d4c07de13b0f0e5533ca0d456b2ea3cf1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for font-hub (version 1.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging font-hub across your stack and pipelines.
If you installed it — respond
font-hub is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If font-hub was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks font-hub before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. font-hub on npm has been identified as a malicious package (version 1.5.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010262

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks font-hub-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database