Which versions of broadcast-graphics-mcp are malicious?

The following npm versions of broadcast-graphics-mcp are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate broadcast-graphics-mcp if I installed it?

broadcast-graphics-mcp 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 broadcast-graphics-mcp — how do I know if it already compromised me?

If broadcast-graphics-mcp 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 broadcast-graphics-mcp part of a known attack campaign?

Yes — broadcast-graphics-mcp is associated with the IN-MAL-2026-018328 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 broadcast-graphics-mcp 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 broadcast-graphics-mcp (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 broadcast-graphics-mcp across your stack and pipelines.

Malicious package

broadcast-graphics-mcpnpm

broadcast-graphics-mcp is a confirmed malicious npm package (MAL-2026-14228) 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 broadcast-graphics-mcp (npm)

MAL-2026-14228

Immediate action

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

npm uninstall broadcast-graphics-mcp

What this malware does

The package's postinstall script runs automatically on npm install and collects host identifiers from the installer machine (os.hostname(), platform, arch, node version, package name, npm lifecycle event, timestamp), then POSTs them as JSON to the hardcoded host 2obx43du.instances.poc.jchunt.top at path /broadcast-graphics-mcp. The destination is not a first-party or user-configurable endpoint; installation of the package unconditionally leaks installer-side identity data to a remote party. The package self-labels as a 'security research canary', but self-labeling does not change the behavior: installing this package causes install-time exfiltration of host metadata to an author-controlled endpoint.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

48987a1a0ccff7dce1134e1a98122cd902961ac34ba623ae0e2fef62f75fe213

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 broadcast-graphics-mcp (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 broadcast-graphics-mcp across your stack and pipelines.
If you installed it — respond
broadcast-graphics-mcp 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 broadcast-graphics-mcp 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 broadcast-graphics-mcp 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. broadcast-graphics-mcp 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-018328

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks broadcast-graphics-mcp-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