Which versions of wix-reg-poc-bypass are malicious?

The following npm versions of wix-reg-poc-bypass are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate wix-reg-poc-bypass if I installed it?

wix-reg-poc-bypass establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed wix-reg-poc-bypass — how do I know if it already compromised me?

If wix-reg-poc-bypass 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 wix-reg-poc-bypass part of a known attack campaign?

Yes — wix-reg-poc-bypass is associated with the IN-MAL-2026-021274 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 wix-reg-poc-bypass across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wix-reg-poc-bypass (version 1.0.0).

Malicious package

wix-reg-poc-bypassnpm

Advisory published Oct 9, 2026Updated Oct 9, 2026

wix-reg-poc-bypass is a confirmed malicious npm package (MAL-2026-17711) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wix-reg-poc-bypass (npm)

MAL-2026-17711

Immediate action

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

npm uninstall wix-reg-poc-bypass

What this malware does

The package shadows internal Wix registry module names (thunderboltRegistry, corvidRegistry, editorRegistry, siteAssetsRegistry, and others) and ships a registry-manifest.min.json pointing at a parastorage CDN URL so that loading one of these registry entries resolves to this package's code. thunderboltRegistry.js runs an IIFE at module load that executes id and hostname via child_process.execSync, combines the output with process.platform, process.arch, process.pid, and process.version, and sends the values as query-string parameters in a fetch() call to the hardcoded collector https://webhook.site/43022177-de67-4d5c-a6df-33083b2b026f. The exported factories return Proxy stubs rather than implementing the real registry contracts, so the module's only effective behavior when loaded by a Wix SSR host is the reconnaissance beacon.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

4b0b4a2bb63a48ca7c9f712068de893526ec0e3515ffd367f37b5c251034965a

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for wix-reg-poc-bypass (version 1.0.0).
If you installed it — respond
wix-reg-poc-bypass establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If wix-reg-poc-bypass 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. wix-reg-poc-bypass 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-021274

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks wix-reg-poc-bypass-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database