Which versions of workvivo-anniversary-automation are malicious?

The following npm versions of workvivo-anniversary-automation are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate workvivo-anniversary-automation if I installed it?

Remove workvivo-anniversary-automation 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 workvivo-anniversary-automation — how do I know if it already compromised me?

If workvivo-anniversary-automation 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 workvivo-anniversary-automation part of a known attack campaign?

Yes — workvivo-anniversary-automation is associated with the RLMA-2025-06539 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 workvivo-anniversary-automation across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for workvivo-anniversary-automation (version 0.0.1).

Malicious package

workvivo-anniversary-automationnpm

Advisory published Dec 23, 2025Updated Jan 2, 2026

workvivo-anniversary-automation is a confirmed malicious npm package (MAL-2025-192886) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in workvivo-anniversary-automation (npm)

MAL-2025-192886

Immediate action

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

npm uninstall workvivo-anniversary-automation

What this malware does

The package workvivo-anniversary-automation was found to contain malicious code.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d009d3258f05407d34d3b771b6a15b489d838f7205cb32e50bb0c05303e75f47

96fc38a568d53764286b6b7ac3292b2c8f8f0c51306b124532a57300399a10a1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for workvivo-anniversary-automation (version 0.0.1).
If you installed it — respond
Remove workvivo-anniversary-automation 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 workvivo-anniversary-automation 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. workvivo-anniversary-automation on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06539

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks workvivo-anniversary-automation-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