Which versions of dom-focus-sentinel are malicious?

The following npm versions of dom-focus-sentinel are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate dom-focus-sentinel if I installed it?

dom-focus-sentinel 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 dom-focus-sentinel — how do I know if it already compromised me?

If dom-focus-sentinel was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dom-focus-sentinel part of a known attack campaign?

Yes — dom-focus-sentinel is associated with the IN-MAL-2026-020975 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 dom-focus-sentinel across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dom-focus-sentinel (version 1.0.0).

Malicious package

dom-focus-sentinelnpm

Advisory published Oct 4, 2026Updated Oct 4, 2026

dom-focus-sentinel is a confirmed malicious npm package (MAL-2026-17503) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dom-focus-sentinel (npm)

MAL-2026-17503

Immediate action

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

npm uninstall dom-focus-sentinel

What this malware does

thunderboltRegistry.js runs an immediately-invoked function at module load that uses child_process.execSync to run host reconnaissance commands (whoami, id, pwd, ifconfig, ip addr, cat /etc/hosts, hostname) and transmits each command's output, along with Node version, platform, and pid, via fetch GET requests to the hardcoded plain-HTTP endpoint http://dxpoc.gt.tc/callback.php/ef9ea0e191006f3cc6670720c99c26f3. The package also structurally impersonates Wix internal registry modules by exporting factories keyed on thunderboltRegistry/siteAssetsRegistry/documentManagementRegistry/editorRegistry/corvidRegistry and shipping a manifest with static.parastorage.com unpkg URLs under [email protected], so the exfiltration IIFE fires whenever a consumer requires any of these registry names. The reconnaissance behavior is unrelated to the declared focus-sentinel purpose, and a beacon=rce-poc marker is embedded in the exfil traffic.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7baf5178b3cd02ae8e6e2c01e8cf305fd9670118428c4d3ef94ac0caef6fc4e8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for dom-focus-sentinel (version 1.0.0).
If you installed it — respond
dom-focus-sentinel 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 dom-focus-sentinel was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. dom-focus-sentinel on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020975

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dom-focus-sentinel-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

Explore

All malware advisories How O3 detects malware Vulnerability database