Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @taxify published 10 malicious packages. See the full campaign →
Malicious package

@taxify/trippricingoptnpm

@taxify/trippricingopt is a confirmed malicious npm package (MAL-2024-9477) that executes malicious code on install (malicious versions 8.999.0, 10.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @taxify/trippricingopt (npm)

MAL-2024-9477
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @taxify/trippricingopt

Malicious versions

2 flagged
8.999.010.0.5

Indicators of compromise (SHA-256)

78e5c9545f68fae8c05ee883ee02a770b58ba663b5477ac3aa1bb1bcddb3ad58

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

  2. If you installed it — respond

    Remove @taxify/trippricingopt 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 @taxify/trippricingopt 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 @taxify/trippricingopt 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. @taxify/trippricingopt on npm has been identified as a malicious package (versions 8.999.0, 10.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-06056

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @taxify/trippricingopt-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

@taxify/trippricingopt (npm) malicious package — MAL-2024-9477 | O3 Security