Which versions of parcel-plugin-asset-copier are malicious?

The following npm versions of parcel-plugin-asset-copier are flagged malicious: 1.1.2, 1.1.3. Treat any of these as compromised.

How do I remediate parcel-plugin-asset-copier if I installed it?

parcel-plugin-asset-copier 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 parcel-plugin-asset-copier — how do I know if it already compromised me?

If parcel-plugin-asset-copier 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 parcel-plugin-asset-copier part of a known attack campaign?

Yes — parcel-plugin-asset-copier is associated with the GHSA-48jp-f8c9-6wqq 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 parcel-plugin-asset-copier 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 parcel-plugin-asset-copier (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging parcel-plugin-asset-copier across your stack and pipelines.

Malicious package

parcel-plugin-asset-copiernpm

Malicious code in parcel-plugin-asset-copier (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190984

Immediate action

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

npm uninstall parcel-plugin-asset-copier

What this malware does

The package parcel-plugin-asset-copier was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.1.21.1.3

Indicators of compromise (SHA-256)

673f23e65b796cf4a1f8f154217b20f06b26d1f7967750091d901380934e2697

344955077c61592ec46c29550b12878886b0b61f3a7c84e050d6d25756f60bf2

e42728295cc2275c35ab041bfdfdad2142156224d4fbdfd267579151fd88834a

f6145ffe2d6b38dc9026fe85b17a49241195565c7383d70aade358ccd4b991ea

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 parcel-plugin-asset-copier (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging parcel-plugin-asset-copier across your stack and pipelines.
If you installed it — respond
parcel-plugin-asset-copier 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 parcel-plugin-asset-copier 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 parcel-plugin-asset-copier 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. parcel-plugin-asset-copier on npm has been identified as a malicious package (versions 1.1.2, 1.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-48jp-f8c9-6wqq

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks parcel-plugin-asset-copier-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