Which versions of a2a-chat-canvas are malicious?

The following npm versions of a2a-chat-canvas are flagged malicious: 97.9.9. Treat any of these as compromised.

How do I remediate a2a-chat-canvas if I installed it?

a2a-chat-canvas 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 a2a-chat-canvas — how do I know if it already compromised me?

If a2a-chat-canvas 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 a2a-chat-canvas part of a known attack campaign?

Yes — a2a-chat-canvas is associated with the GHSA-pf4w-8h65-5h66 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 a2a-chat-canvas 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 a2a-chat-canvas (version 97.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging a2a-chat-canvas across your stack and pipelines.

Malicious package

a2a-chat-canvasnpm

a2a-chat-canvas is a confirmed malicious npm package (MAL-2026-2524) that steals credentials and exfiltrates sensitive data (malicious version 97.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in a2a-chat-canvas (npm)

MAL-2026-2524

Immediate action

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

npm uninstall a2a-chat-canvas

What this malware does

Malicious package due to suspicious callback URL, hostname exfiltration, preinstall script execution, and only one published version.

The package a2a-chat-canvas 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.

Malicious versions

1 flagged

97.9.9

Indicators of compromise (SHA-256)

d466a45c588940f8279288c439a4665d5368f0a7642c966de8e9fd307bc028b3

f00e715dfd6edea72333ace82efe5a1aad300d4ef499fced9cd6252d147259d6

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

Campaign

GHSA-pf4w-8h65-5h66

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks a2a-chat-canvas-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