Which versions of dom-weave are malicious?

Every published version of dom-weave on npm is considered malicious. Remove the package entirely.

How do I remediate dom-weave if I installed it?

Remove dom-weave from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed dom-weave — how do I know if it already compromised me?

If dom-weave 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-weave part of a known attack campaign?

Yes — dom-weave is associated with the GHSA-wx59-xwhx-3mmv 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-weave across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dom-weave (all published versions).

Malicious package

dom-weavenpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

dom-weave is a confirmed malicious npm package (MAL-2026-10561) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dom-weave (npm)

MAL-2026-10561

Immediate action

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

npm uninstall dom-weave

What this malware does

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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

1e8a695176c5bf53d1e63c28f3ecfe9038d831e2ad4e063de45a04252976bd9f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dom-weave (all published versions).
If you installed it — respond
Remove dom-weave from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dom-weave 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-weave on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wx59-xwhx-3mmv

References

github.com

Detect & block this

O3 blocks dom-weave-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database