Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@next-fonts/fontnpm

Advisory published Updated

@next-fonts/font is a confirmed malicious npm package (MAL-2026-14346) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @next-fonts/font (npm)

MAL-2026-14346
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @next-fonts/font

What this malware does

@next-fonts/font is a typosquat of Next.js's @next/font. Its exported Inter() function (mimicking next/font/google) decodes a base64 blob via atob(), then executes it through spawn('node','-e', code) with an eval(code) fallback. The decoded payload uses on-chain data as a C2 channel: it queries api.trongrid.io or fullnode.mainnet.aptoslabs.com for a transaction tied to hardcoded wallet addresses, retrieves that transaction's input data from BSC RPC endpoints (bsc-dataseed.binance.org, bsc-rpc.publicnode.com) via eth_getTransactionByHash, XOR-decrypts the returned bytes, and evals the resulting JavaScript. The result is arbitrary attacker-controlled code execution on any Node process that imports the package and invokes Inter(), with no relation to font functionality. Obfuscation (base64-hidden payload, node -e detached spawn with eval fallback, blockchain-mediated fetch) conceals the downloader from casual inspection.

Malicious versions

2 flagged
1.0.01.0.1

Indicators of compromise (SHA-256)

1165fecff800f58383c09762935267dddab4d21d37f6166d4e3ceaf0d9175191
4e536e77176d5fb4637105c50280763e82a6a273dd7de35bb82da340b0f71163

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @next-fonts/font (2 malicious versions).

  2. If you installed it — respond

    @next-fonts/font 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.

  3. Did it already run?

    If @next-fonts/font was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @next-fonts/font on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018501IN-MAL-2026-018502

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

@next-fonts/font (npm) malicious package — MAL-2026-14346 | O3 Security