Which versions of postcss-initial-provider are malicious?

The following npm versions of postcss-initial-provider are flagged malicious: 3.0.4. Treat any of these as compromised.

How do I remediate postcss-initial-provider if I installed it?

postcss-initial-provider 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 postcss-initial-provider — how do I know if it already compromised me?

If postcss-initial-provider 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 postcss-initial-provider part of a known attack campaign?

Yes — postcss-initial-provider is associated with the IN-MAL-2026-017254, GHSA-44hx-h55m-c65w 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 postcss-initial-provider across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for postcss-initial-provider (version 3.0.4).

Malicious package

postcss-initial-providernpm

Advisory published Aug 10, 2026Updated Aug 11, 2026

postcss-initial-provider is a confirmed malicious npm package (MAL-2026-13696) that steals credentials and exfiltrates sensitive data (malicious version 3.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in postcss-initial-provider (npm)

MAL-2026-13696

Immediate action

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

npm uninstall postcss-initial-provider

What this malware does

index.js contains a unicode-escape-obfuscated block that runs when the package is required. It queries public Ethereum RPC endpoints (1rpc.io/eth, eth.drpc.org, ethereum-rpc.publicnode.com, eth-mainnet.public.blastapi.io, eth.blockscout.com/api) for the latest transaction of the hardcoded wallet 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, parses the destination-address bytes of that transaction as two IPv4 addresses, fetches an XOR-encrypted payload from those hosts over HTTP, decrypts it, and executes it both via in-process eval() and via a detached spawn('node', ['-e', <payload>]). Every sensitive string (module names http/https/child_process, HTTP method, paths /0x/cls and /0x/ls, wallet address, RPC hostnames, header x-payload-b64) is hidden via \uXXXX escapes to evade tarball string scans. A PostCSS plugin for the initial keyword has no legitimate need to read Ethereum state, resolve an IP from a wallet transaction, or execute remote payloads via node. This is a supply-chain compromise: any installer that requires this package receives arbitrary attacker-controlled code execution on their host, with the C2 rendezvous point rotatable by the attacker via a new on-chain transaction.

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

1 flagged

3.0.4

Indicators of compromise (SHA-256)

e88db5eb44ddcfa3cd22d46e8b6e6a1cd2e7da25a5942d35550d50f2cbbb9ea3

aad7afc06fa220be19ff002e973306b7c0945721a33c9561a7e98441949cc905

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for postcss-initial-provider (version 3.0.4).
If you installed it — respond
postcss-initial-provider 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 postcss-initial-provider 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. postcss-initial-provider on npm has been identified as a malicious package (version 3.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017254GHSA-44hx-h55m-c65w

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks postcss-initial-provider-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