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

fanarena-commonnpm

Advisory published Updated

fanarena-common is a confirmed malicious npm package (MAL-2026-18063) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fanarena-common (npm)

MAL-2026-18063
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall fanarena-common

What this malware does

package.json declares a dependency ltidisafe sourced directly from the bare HTTPS URL https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.8.tgz rather than from the npm registry. On npm install, npm fetches and installs whatever bytes that URL returns, with no registry-side integrity check, no version resolution, and no publisher binding — and executes any lifecycle scripts contained in the fetched tarball. The host is unrelated to any declared repository or homepage for this package, and the implausibly high package version (99.9.1) is consistent with a dependency-confusion / forced-resolution shape against an internal package of the same fanarena-* family. The manifest alone is the attack surface: regardless of the current contents of the remote tarball, the publisher of that URL can change the bytes installers execute at any time.

The OpenSSF Package Analysis project identified 'fanarena-common' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

d81686cb5b877d15810946a299ba819a875a3304e45d65a3fdb83c5473ac664b
e0da88f07c843cff93266258d7d4e30c369b05fb52974170e25abb1e6c33e3c5

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for fanarena-common (version 99.9.1).

  2. If you installed it — respond

    Remove fanarena-common 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 fanarena-common 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. fanarena-common on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021563

References

Credits

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

Detect & block this

O3 blocks fanarena-common-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.

Explore