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

@airbnb-extended/typescript-confignpm

@airbnb-extended/typescript-config is a confirmed malicious npm package (MAL-2026-17184) that typosquats a legitimate package to trick installs (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @airbnb-extended/typescript-config (npm)

MAL-2026-17184
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @airbnb-extended/typescript-config

What this malware does

package.json for @airbnb-extended/[email protected] declares a dependency ltidisafe sourced from a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.7.8.tgz) instead of a registry version range. On npm install, npm fetches and installs whatever bytes that URL returns, executing any lifecycle scripts inside the fetched tarball. The source is unpinned by integrity hash, is not the npm registry, and is unrelated to any Airbnb-published infrastructure. The scope/name also mimics the well-known @airbnb/typescript-config package, and the version 99.9.1 is implausibly high — a dependency-confusion / lure shape designed to win resolution against a legitimate internal or public package. The tarball URL is mutable by whoever controls the storage bucket, so the delivered payload can change at any time.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

8424e4bf8731b950511535a2cb9b41b0bedba02092a73ea304b6730f04aa95fe

Detection & response playbook

Typosquat
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @airbnb-extended/typescript-config (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 @airbnb-extended/typescript-config across your stack and pipelines.

  2. If you installed it — respond

    @airbnb-extended/typescript-config is a typosquat — you almost certainly intended a legitimately-named package. Remove @airbnb-extended/typescript-config, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If @airbnb-extended/typescript-config 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 @airbnb-extended/typescript-config 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. @airbnb-extended/typescript-config 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-020561

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @airbnb-extended/typescript-config-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

@airbnb-extended/typescript-config (npm) malicious package — MAL-2026-17184 | O3 Security