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

@global-dax-ad-platform/dax-componentsnpm

Malicious code in @global-dax-ad-platform/dax-components (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1165
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @global-dax-ad-platform/dax-components

What this malware does

The package @global-dax-ad-platform/dax-components 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

3 flagged
99.99.9999.999.9999999.999.999

Indicators of compromise (SHA-256)

bfee295f8f4a56cfda5ac5bf356fc12667a8e371591b0c2d020f826e66237aa1
e50b13916c14b17a01e550d32711ed37f8842bc2a0eede3ea254df64f7a0af1a
9600b297b7671600050e918ec07cd1299691aa55db97b1dcf8600ffadeb44ded
7b4488629c567845b60f37bf7ae99774e63272bfee1ec0ebecd20584aba5a0b2

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 @global-dax-ad-platform/dax-components (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @global-dax-ad-platform/dax-components across your stack and pipelines.

  2. If you installed it — respond

    Remove @global-dax-ad-platform/dax-components 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 @global-dax-ad-platform/dax-components 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 @global-dax-ad-platform/dax-components 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. @global-dax-ad-platform/dax-components on npm has been identified as a malicious package (versions 99.99.9, 999.999.999, 9999.999.999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5rpp-4wg3-q4wwRLMA-2026-01007RLUA-2026-01696

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @global-dax-ad-platform/dax-components-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.

Malware detection Runtime egress monitoring
@global-dax-ad-platform/dax-components (npm) malicious package — MAL-2026-1165 | O3 Security