Malicious code in @engagehub/core (npm)
Source: amazon-inspector
All three lifecycle hooks (preinstall, install, postinstall) in package.json invoke node telemetry.js, so the payload fires unconditionally on npm install. telemetry.js gathers host context (OS, arch, Node version, pid) and CI-provider fingerprints by reading GITHUB_ACTIONS, AZURE_DEVOPS, and JENKINS_HOME, hex-encodes a JSON blob, and exfiltrates it as chunked dns.lookup() queries whose subdomain labels carry the encoded data. The destination is built via string concatenation to evade scanners: "d82atu5fokal0459"+"5n00qkgj7qiyixx7a"+"."+"oa"+"st"+"."+"li"+"ve", resolving to a token under oast.live — an out-of-band interaction (interactsh) service commonly used by attackers as a covert DNS C2/exfil channel. The package additionally impersonates Microsoft (false Copyright (c) Microsoft Corporation header, fabricated github.com/microsoft/core repository URL, references to a nonexistent engdocs.microsoft.com docs site) under an UNLICENSED license to lend credibility to the dropper. Installing this package on a developer workstation or CI runner leaks host and CI-environment fingerprints to attacker-controlled infrastructure and confirms the package is reachable for follow-on targeting.
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 '@engagehub/core' @ 99.0.0 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
