Which versions of @divineubg/divine are malicious?

The following npm versions of @divineubg/divine are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate @divineubg/divine if I installed it?

@divineubg/divine establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @divineubg/divine — how do I know if it already compromised me?

If @divineubg/divine 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 @divineubg/divine part of a known attack campaign?

Yes — @divineubg/divine is associated with the IN-MAL-2026-017913 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 @divineubg/divine 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 @divineubg/divine (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @divineubg/divine across your stack and pipelines.

Malicious package

@divineubg/divinenpm

@divineubg/divine is a confirmed malicious npm package (MAL-2026-14043) that opens a backdoor for remote access (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @divineubg/divine (npm)

MAL-2026-14043

Immediate action

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

npm uninstall @divineubg/divine

What this malware does

index.js exports a listen(clientId) function that subscribes to https://ntfy.sh/dv-141u30-admin-cmd-<clientId>/sse via EventSource and, on receiving messages with action 'EVAL_CODE', passes the message payload to eval() and new Function() — executing attacker-supplied JavaScript in the loading context. Execution results are POSTed back to https://ntfy.sh/dv-141u30-admin-status-<clientId>. The clientId is a 7-digit value persisted in localStorage as g_live_username. Any application bundling this package ships a remote command-and-control channel to end-user browsers: whoever knows or enumerates a client's topic can run arbitrary JavaScript in that browser and receive the results, with no integrity check, origin restriction, or user confirmation.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

52dc0a48d6e7e18ff3bb09306aa6d4c17aefff323b1f86b84f19197ba4a094be

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @divineubg/divine (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @divineubg/divine across your stack and pipelines.
If you installed it — respond
@divineubg/divine establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @divineubg/divine 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 @divineubg/divine 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. @divineubg/divine on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017913

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @divineubg/divine-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database