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

frontend-google-tag-managernpm

frontend-google-tag-manager is a confirmed malicious npm package (MAL-2025-48278) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in frontend-google-tag-manager (npm)

MAL-2025-48278
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall frontend-google-tag-manager

What this malware does

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.0.0

Indicators of compromise (SHA-256)

a4f6a0228c6c8a63f058b39d72aa7f23d1f92b03e46a8f5dff1b1f856bbb6306
e3f9ea73e75952aa8ac4ebe25b322f5437fdb8cf68e6d8a30edbb134f9be86bc
0b593f8bcb10a674d9098ba2fef9c855e079470f9b0e337bd0fd94fdd6e50024

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 frontend-google-tag-manager (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging frontend-google-tag-manager across your stack and pipelines.

  2. If you installed it — respond

    Remove frontend-google-tag-manager 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 frontend-google-tag-manager 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 frontend-google-tag-manager 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. frontend-google-tag-manager on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5hp8-gm4x-wf3pRLMA-2025-05372RLUA-2025-05798

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks frontend-google-tag-manager-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.

Explore

frontend-google-tag-manager (npm) malicious package — MAL-2025-48278 | O3 Security