connect-contingency
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-3q7q-6272-2v37
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in connect-contingency (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (b3a03c555705f2bfa2e63b96e9ea5740196d1ea5ca8be0f1acce290c771f01ea)
[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.
Source: ghsa-malware (53d8e8bca85cba82ba9b06a3823185e95fd07fc484de0701f83f76a4be427a76)
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0