Which versions of capacitor-assets are malicious?

The following npm versions of capacitor-assets are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate capacitor-assets if I installed it?

capacitor-assets 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 capacitor-assets — how do I know if it already compromised me?

If capacitor-assets 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 capacitor-assets part of a known attack campaign?

Yes — capacitor-assets is associated with the GHSA-8v58-g8f8-2gpp, IN-MAL-2026-012884 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 capacitor-assets 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 capacitor-assets (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 capacitor-assets across your stack and pipelines.

Malicious package

capacitor-assetsnpm

capacitor-assets is a confirmed malicious npm package (MAL-2026-11457) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in capacitor-assets (npm)

MAL-2026-11457

Immediate action

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

npm uninstall capacitor-assets

What this malware does

Package name typosquats the legitimate @capacitor/assets. On postinstall (via postinstall.js invoking lib/report.js), the package collects developer identity information — email harvested via gh api/git config/npm config, OS username from os.userInfo(), and hostname from os.hostname() — and POSTs it as JSON to a hardcoded author-controlled Zapier webhook at https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. lib/report.js requires child_process, https, fs, and os; uses execSync to invoke git/gh/npm to extract the developer's email, and https.request to transmit. The postinstall path is gated by a consent flag stored in ~/.install-email-research.json and a CLI prompt, but the package's name-confusion with a well-known Capacitor scope combined with a hardcoded author endpoint receiving developer identity fields matches the credential/identity-harvest shape rather than legitimate telemetry. No opt-in disclosure exists in the package name or README before install, and the destination is a generic Zapier catch hook rather than an identifiable vendor endpoint.

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

1.0.0

Indicators of compromise (SHA-256)

9b3684fbb41e490eea74489dc2453b1f37022ced6d2fba0c72a82ebbc42f4f80

02650efb5b0f2e8ca581f927c0ca3e50966bc8b425e81a6e2dc9f45c70234422

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 capacitor-assets (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 capacitor-assets across your stack and pipelines.
If you installed it — respond
capacitor-assets 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 capacitor-assets 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 capacitor-assets 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. capacitor-assets 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

GHSA-8v58-g8f8-2gppIN-MAL-2026-012884

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks capacitor-assets-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