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

@global-dax-ad-platform/dax-typesnpm

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

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

What this malware does

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

f5d5c2af3656b50f9dddf3a86f3b2c15492e742303357ca994ad03a7ae56b637
465668b4ba6f4c109320a3407a4db8d254d21a7f43af75ca5f8c1873c12c7f46
c4d1884d66cab4eb31b5a8e2576826a2514bd3e6ec97fff6caf290e5e52bceca
4043a032791c3cec9d1c56c3cc0d9381f13bb715b42418e64d59b7b7f4c843ba

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-types (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-types across your stack and pipelines.

  2. If you installed it — respond

    Remove @global-dax-ad-platform/dax-types 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-types 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-types 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-types 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-w8f2-jmmq-3g88RLMA-2026-01011RLUA-2026-01700

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

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