What does the @taxify/smartpickups malware do?

The OpenSSF Package Analysis project identified '@taxify/smartpickups' @ 9.999.0 (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.

Which versions of @taxify/smartpickups are malicious?

The following npm versions of @taxify/smartpickups are flagged malicious: 8.999.0, 9.999.0, 10.0.0, 10.0.1. Treat any of these as compromised.

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

Remove @taxify/smartpickups 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/smartpickups — how do I know if it already compromised me?

If @taxify/smartpickups 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.

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

Yes — @taxify/smartpickups is associated with the RLMA-2024-06053 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/smartpickups across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @taxify/smartpickups (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @taxify/smartpickups across your stack and pipelines.

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

Malicious package

@taxify/smartpickupsnpm

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

Malicious code in @taxify/smartpickups (npm)

MAL-2024-7899

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @taxify/smartpickups

What this malware does

The OpenSSF Package Analysis project identified '@taxify/smartpickups' @ 9.999.0 (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

8.999.09.999.010.0.010.0.1

Indicators of compromise (SHA-256)

9d20e7ecf4639b1082be1a46fec756d84cc7d8fc35310af0e6af87e19879fcf7

5fa6420ceb51b8ece3751b9fa9064288fcf5dce1c0e03513afef21f0de192176

49a6b590f70d6795c4456775b23ab6cf5465c929aee73821ed2f9d42ad522df4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @taxify/smartpickups (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @taxify/smartpickups across your stack and pipelines.
If you installed it — respond
Remove @taxify/smartpickups 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/smartpickups 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.
How O3 protects you
O3 blocks @taxify/smartpickups 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/smartpickups on npm has been identified as a malicious package (versions 8.999.0, 9.999.0, 10.0.0, 10.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-06053

Credits

OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

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