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

@global-dax-ad-platform/dax-modulesnpm

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

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

What this malware does

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

e175667b4b1ead19f1ca6945768e39920a588fddcd86825c08d7cef4b9d8fd63
8eb4c0cce0e997a5ceaf51dd24ec685c500bbfe904265afdce79bb5b2f7e0033
c1bed776fa2e0beb1091cd1e24bd97b40cf9b8c86e5d180d59fc5c277896991d
87dd44d39d121937780472c70b6f4b0827421e1ce399e5324444c85142709858

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

  2. If you installed it — respond

    Remove @global-dax-ad-platform/dax-modules 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-modules 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-modules 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-modules 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-rqrg-p585-r9f4RLMA-2026-01009RLUA-2026-01698

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @global-dax-ad-platform/dax-modules-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-modules (npm) malicious package — MAL-2026-1167 | O3 Security