Which versions of async-chain-dom are malicious?

The following npm versions of async-chain-dom are flagged malicious: 1.3.5. Treat any of these as compromised.

How do I remediate async-chain-dom if I installed it?

async-chain-dom is a typosquat — you almost certainly intended a legitimately-named package. Remove async-chain-dom, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — async-chain-dom is associated with the IN-MAL-2026-009831 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 async-chain-dom 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 async-chain-dom (version 1.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging async-chain-dom across your stack and pipelines.

Malicious package

async-chain-domnpm

Malicious code in async-chain-dom (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10406

Immediate action

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

npm uninstall async-chain-dom

What this malware does

On require, index.js spawns a detached, unref'd node lib/vcall.js child process. lib/vcall.js fetches JavaScript from https://api.jsonsilo.com/public/df71fd55-4f0c-4326-9b5b-a285e38023a5, extracts the .model field from the response, and executes it via new Function.constructor("require", src) with require passed in, giving the remote endpoint arbitrary code execution inside the installer's Node process. The detached+unref pattern decouples the loader from the parent lifecycle so it persists after the consumer process exits, and a retry loop keeps the fetch running. The package masquerades as the pino logger (module.exports.pino = vCheck; keywords fast/logger/stream/json; lib files mimicking pino) despite the name async-chain-dom, providing a cover story for a developer to require it. The remote endpoint is a mutable jsonsilo.com blob under attacker control, so the executed payload can be swapped at any time.

Malicious versions

1 flagged

1.3.5

Indicators of compromise (SHA-256)

0f2ce6eed4ea7607d2f12f602b43b354b91ceba4cabdc761f569c3e1dc29b6f6

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for async-chain-dom (version 1.3.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging async-chain-dom across your stack and pipelines.
If you installed it — respond
async-chain-dom is a typosquat — you almost certainly intended a legitimately-named package. Remove async-chain-dom, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If async-chain-dom 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 async-chain-dom 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. async-chain-dom on npm has been identified as a malicious package (version 1.3.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009831

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks async-chain-dom-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