Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@platform-growth/guidance-channel-providernpm

Malicious code in @platform-growth/guidance-channel-provider (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1302
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @platform-growth/guidance-channel-provider

What this malware does

The package @platform-growth/guidance-channel-provider 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
99.99.0

Indicators of compromise (SHA-256)

cc8e13c7b4eece29e21aa78b4e479975d37b8d58baacba239cbae0bcfc4d2ad1
e534a225d1762fbd8fb95884b7532f2086caa289358fc90d75b28ee30f21a781
851a1eb428b30069bd6ba251018b1547db4c6066228663539c2b80b07ba0061e
a151faf5c717385aa033ff5b268c5f8c52a042f92322795c55071f3fba93c026

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @platform-growth/guidance-channel-provider (version 99.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @platform-growth/guidance-channel-provider across your stack and pipelines.

  2. If you installed it — respond

    Remove @platform-growth/guidance-channel-provider from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @platform-growth/guidance-channel-provider 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.

  4. How O3 protects you

    O3 blocks @platform-growth/guidance-channel-provider 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. @platform-growth/guidance-channel-provider on npm has been identified as a malicious package (version 99.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m84f-rg3g-9pvwRLMA-2026-01045RLUA-2026-01706

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @platform-growth/guidance-channel-provider-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

@platform-growth/guidance-channel-provider (npm) malicious package — MAL-2026-1302 | O3 Security