Which versions of @taxify/trippricingopt are malicious?

The following npm versions of @taxify/trippricingopt are flagged malicious: 8.999.0, 10.0.5. Treat any of these as compromised.

How do I remediate @taxify/trippricingopt if I installed it?

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.

I already installed @taxify/trippricingopt — how do I know if it already compromised me?

If @taxify/trippricingopt was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @taxify/trippricingopt part of a known attack campaign?

Yes — @taxify/trippricingopt is associated with the RLMA-2024-06056 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @taxify/trippricingopt across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @taxify/trippricingopt (2 malicious versions).

Part of a larger attack: @taxify published 10 malicious packages. See the full campaign →

Malicious package

@taxify/trippricingoptnpm

Advisory published Oct 16, 2024Updated Oct 16, 2024

@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

Find it
Search your lockfiles and build artifacts for @taxify/trippricingopt (2 malicious versions).
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.
Did it already run?
If @taxify/trippricingopt was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database