Which versions of @dxcl/transaction-js are malicious?

The following npm versions of @dxcl/transaction-js are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate @dxcl/transaction-js if I installed it?

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

If @dxcl/transaction-js 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 @dxcl/transaction-js part of a known attack campaign?

Yes — @dxcl/transaction-js is associated with the RLMA-2026-05419, RLUA-2026-05856 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 @dxcl/transaction-js across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @dxcl/transaction-js (version 99.99.99).

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

Malicious package

@dxcl/transaction-jsnpm

Advisory published Jul 20, 2026Updated Sep 1, 2026

@dxcl/transaction-js is a confirmed malicious npm package (MAL-2026-10878) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @dxcl/transaction-js (npm)

MAL-2026-10878

Immediate action

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

npm uninstall @dxcl/transaction-js

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

f5dc812cf8e1b485f0a5991a6b9406e8392a98e7f43f05e9e0e1d00f0fbc123d

f937170715d4950cd4939160bfec8cdabfc08e9e7ba4463b9b3e2a003775d87e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05419RLUA-2026-05856

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @dxcl/transaction-js-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