Which versions of @engagehub/core are malicious?

The following npm versions of @engagehub/core are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @engagehub/core if I installed it?

@engagehub/core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @engagehub/core — how do I know if it already compromised me?

If @engagehub/core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @engagehub/core part of a known attack campaign?

Yes — @engagehub/core is associated with the IN-MAL-2026-004252, IN-MAL-2026-004251 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @engagehub/core across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @engagehub/core (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @engagehub/core across your stack and pipelines.

Malicious package

@engagehub/corenpm

Malicious code in @engagehub/core (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4258

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @engagehub/core

What this malware does

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.

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.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

326b05b76110daa7a72638fd81d726fb2ccb229f93e203e07aa236639b9120fa

00d2aa8784139f3335dd28e4b761b1f90459d3ff18f4e531d1f26287b05510be

bcc397ed87426726776c339f950939ac2da46c12edd018ed4bc48031f7044094

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @engagehub/core (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @engagehub/core across your stack and pipelines.
If you installed it — respond
@engagehub/core is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @engagehub/core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @engagehub/core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @engagehub/core on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004252IN-MAL-2026-004251

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @engagehub/core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring