Which versions of xarc-webpack-cli are malicious?

The following npm versions of xarc-webpack-cli are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate xarc-webpack-cli if I installed it?

xarc-webpack-cli 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 xarc-webpack-cli — how do I know if it already compromised me?

If xarc-webpack-cli 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 xarc-webpack-cli part of a known attack campaign?

Yes — xarc-webpack-cli is associated with the IN-MAL-2026-004782, IN-MAL-2026-004781, GHSA-2xcr-5qfc-fq54 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 xarc-webpack-cli 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 xarc-webpack-cli (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xarc-webpack-cli across your stack and pipelines.

Malicious package

xarc-webpack-clinpm

Malicious code in xarc-webpack-cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4352

Immediate action

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

npm uninstall xarc-webpack-cli

What this malware does

The package ships a preinstall hook (node poc.js || true) that runs on every npm install. poc.js collects host fingerprint data (hostname, username, os.platform(), network configuration via ipconfig/ip a/resolv.conf, id, whoami), the parent project's package.json, git remote URLs, CI workflow files, and bulk-scrapes process.env for any key matching a hardcoded prefix list (TOKEN, AWS, AZURE, NPM, GITHUB, GITLAB, JENKINS, CI_, WALMART, WMT, etc.). The collected JSON is POSTed over HTTPS to a hardcoded Interactsh out-of-band collector (d8acb4hon5btn99s9lsgakhs31dmwk9cr.oast.pro) plus a DNS callback to the same host. The package name and the inclusion of WALMART/WMT in the env-var harvest list indicate this is dependency-confusion bait targeting Walmart's internal @xarc/* scope; package.json self-describes it as 'authorized dependency confusion testing' but ships with no authorization gate, so any installer that resolves this name has its CI/CD tokens, cloud credentials, and source metadata shipped to the attacker-controlled OOB host.

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.

The OpenSSF Package Analysis project identified 'xarc-webpack-cli' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

b9a1bb4adee0a346eeb247af4ef6569464a634fe87576a149a44f5ececd15d90

2704d8b2d2d258af922882a3b724b2f9e2604964080e294400e1f3879aa46835

b29d869051afe04db57e24dad1092c70992f83465d60989f5120e17d7fa20310

401efd45edfe86b2e2f3c6a0fb591b94bbae8bb50162ebc0c8bd5bfdfaa9e6f6

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 xarc-webpack-cli (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xarc-webpack-cli across your stack and pipelines.
If you installed it — respond
xarc-webpack-cli 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 xarc-webpack-cli 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 xarc-webpack-cli 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. xarc-webpack-cli 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-004782IN-MAL-2026-004781GHSA-2xcr-5qfc-fq54

References

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks xarc-webpack-cli-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