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

@wealth-common/fontnpm

Malicious code in @wealth-common/font (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1458
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @wealth-common/font

What this malware does

The package @wealth-common/font was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

The OpenSSF Package Analysis project identified '@wealth-common/font' @ 99.0.3 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
99.0.3

Indicators of compromise (SHA-256)

c7838c856ef7da8323729d7d5bb10c2ee93735620711853774d34c0d00b1642f
6191139a683489b1030bf094578c1678d196e9b1edbc3b3dec38008677220f22
0a56e089d98a2a90a0e20698b8e57be8f14e4999477967cdf1254cff0e51804c

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove @wealth-common/font from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @wealth-common/font 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.

  4. How O3 protects you

    O3 blocks @wealth-common/font 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. @wealth-common/font on npm has been identified as a malicious package (version 99.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cgmf-p7fr-9qwp

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @wealth-common/font-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

@wealth-common/font (npm) malicious package — MAL-2026-1458 | O3 Security