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

@automation-toolchain/f5-cloud-libsnpm

Malicious code in @automation-toolchain/f5-cloud-libs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2662
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @automation-toolchain/f5-cloud-libs

What this malware does

The package @automation-toolchain/f5-cloud-libs was found to contain malicious code.

The OpenSSF Package Analysis project identified '@automation-toolchain/f5-cloud-libs' @ 4.29.0-2037287d1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

4 flagged
4.29.0-2037287d4.29.0-2037287d199.99.99100.0.0

Indicators of compromise (SHA-256)

0c431accac1c68bd868f333a048c057118717749ef66177b1f1cc948e96d7d78
dc7ef28aac5f83065e97ccf6c1c243f2ac32bd7717cf24345f07da10f66f236d
2bfc189949f1db0cdc70361f74210d6fe3f92c3e69ddad9491d9c7615465f9c6
da0762e03c98a29c520f4c3185889c11e120eace48b8664c790a8769696754a8
ba3406b31c655d265f4de4dde324d557dfe131624127a9d8f90629e8bc6b9433

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 @automation-toolchain/f5-cloud-libs (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @automation-toolchain/f5-cloud-libs across your stack and pipelines.

  2. If you installed it — respond

    Remove @automation-toolchain/f5-cloud-libs 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 @automation-toolchain/f5-cloud-libs 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 @automation-toolchain/f5-cloud-libs 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. @automation-toolchain/f5-cloud-libs on npm has been identified as a malicious package (versions 4.29.0-2037287d, 4.29.0-2037287d1, 99.99.99, 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @automation-toolchain/f5-cloud-libs-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.

@automation-toolchain/f5-cloud-libs (npm) malicious package — MAL-2026-2662 | O3 Security