NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

connect-contingencynpm

Advisory published Updated

connect-contingency is a confirmed malicious npm package (MAL-2026-13440) 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 connect-contingency (npm)

MAL-2026-13440
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall connect-contingency

What this malware does

[email protected] is a hollow package whose index.js is an empty stub. Its package.json declares its sole dependency ltidisafe as a direct tarball URL on an anonymous Google Cloud Storage bucket: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.4.7.tgz. On npm install, npm downloads that tarball from a non-registry, non-publisher host outside registry integrity/audit coverage and installs it, executing any lifecycle scripts (preinstall/install/postinstall) it declares. The package name, an inflated 99.9.x version characteristic of dependency-confusion staging, the empty main, and the /depenconf/ URL path together indicate a dependency-confusion lure whose only effect on install is to pull attacker-controlled code into the installer's environment.

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.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

b3a03c555705f2bfa2e63b96e9ea5740196d1ea5ca8be0f1acce290c771f01ea
53d8e8bca85cba82ba9b06a3823185e95fd07fc484de0701f83f76a4be427a76

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for connect-contingency (version 99.9.1).

  2. If you installed it — respond

    Remove connect-contingency 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 connect-contingency 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. connect-contingency 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-016670GHSA-3q7q-6272-2v37

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks connect-contingency-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

connect-contingency (npm) malicious package — MAL-2026-13440 | O3 Security