sorenson-webfontsnpm
Malicious code in sorenson-webfonts (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
[email protected] is a hollow package: index.js is a 2-line stub ('use strict'; module.exports = {};), author/description fields are empty, and the version number 99.9.1 is the high-version pattern characteristic of dependency-confusion attempts to override an internal package. The package's only effect on install is to pull a single dependency, ltidisafe, directly from an HTTPS tarball URL on a Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.8.2.tgz) — a non-registry, non-publisher location whose path segment depenconf suggests dependency-confusion staging. Resolving this dependency causes npm to fetch and execute the lifecycle scripts of an off-registry tarball whose contents are not pinned by integrity hash and not subject to registry review. The package name (sorenson-webfonts) bears no relation to the dependency name or to any stated purpose; there is no advertised webfont functionality in the shipped code. The combination of empty body, placeholder metadata, 99.9.x version, and an unrelated off-registry tarball pulled from a bucket path named after dependency confusion is the smuggling-vehicle shape rather than a legitimate library.
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 'sorenson-webfonts' @ 99.9.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sorenson-webfonts (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sorenson-webfonts across your stack and pipelines.
If you installed it — respond
Remove sorenson-webfonts 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.
Did it already run?
If sorenson-webfonts 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 sorenson-webfonts 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
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks sorenson-webfonts-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.