confluence-create-contentnpm

package.json declares a dependency whose key equals the package's own name (confluence-create-content) and whose value is a bare HTTPS URL, https://repo.securityctrl.com/confluence-create-content, instead of a registry version range. On npm install, npm fetches whatever bytes that URL returns and installs them, running any lifecycle scripts contained in them with no version pin and no integrity check. The shipped index.js is an inert stub, so the manifest URL is effectively the entire delivered payload. The self-named dependency shape also creates dependency-confusion pressure: any environment resolving this package name pulls content from the third-party host rather than the registry.

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.