🛡️ MAL-2026-5159 — po-ops-local-dev

Malicious code in po-ops-local-dev (npm)

Source: amazon-inspector

[email protected] has no functional code of its own (index.js contains only module.exports = {}; and there are no lifecycle scripts). Its sole effect on install is to pull ltidisafe directly from https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.9.2.tgz — a Google Cloud Storage bucket, not the npm registry. The package name po-ops-local-dev combined with the depenconf path segment in the tarball URL is consistent with a dependency-confusion staging or research artifact. On npm install, npm fetches that tarball and runs any lifecycle scripts it contains; the contents at that GCS URL are mutable and outside npm's integrity verification. The actual installer impact depends entirely on what bytes the GCS bucket serves, which were not inspected here.

Source: ghsa-malware

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.

Source: ossf-package-analysis

The OpenSSF Package Analysis project identified 'po-ops-local-dev' @ 99.9.1 (npm) as malicious.

It is considered malicious because:

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