If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (2fb98ad3575267cc8fbf617fe6a17000ed10df97d39710f4b7aaddf7225598d7)
@postex/common@99.9.1 ships an inert index.js (module.exports = {}) and declares a single dependency `ltidisafe` whose value is a bare HTTPS tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.9.5.tgz) rather than a registry version range. On `npm install`, npm fetches whatever bytes that URL returns, installs the resulting package, and executes any lifecycle scripts it contains, with no registry-mediated integrity, signature, or version pinning. The host (a user-controlled Google Cloud Storage bucket) is unrelated to any npm scope or published repository for this package, and the content served there can change at any time without any change to this manifest. The implausibly high version (99.9.1) combined with a hollow stub and an off-registry source is consistent with a dependency-confusion / smuggling lure whose only install-time effect is resolving to attacker-controlled code.
Source: ghsa-malware (fc23936b2240b9ef6d55f1fb4101f06b61ac33b1f1e8687dc26e6a6f6b9c91d4)
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.