Which versions of divvy-web are malicious?

The following npm versions of divvy-web are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate divvy-web if I installed it?

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

If divvy-web 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 divvy-web part of a known attack campaign?

Yes — divvy-web is associated with the RLMA-2026-05039, RLUA-2026-06175 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 divvy-web across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for divvy-web (version 9.9.9).

Malicious package

divvy-webnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

divvy-web is a confirmed malicious npm package (MAL-2026-7250) that executes malicious code on install (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in divvy-web (npm)

MAL-2026-7250

Immediate action

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

npm uninstall divvy-web

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

56ba048c2c3a3ce20ceca01853701f9f391e5c681913cc0f791dd656f826f900

d4dc53e31ecee7132aed479908dd235825cd6a1181dd2e57f6808d44e6f9393e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05039RLUA-2026-06175

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks divvy-web-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