What does the dex-creator malware do?

The package communicates with a domain associated with malicious activity. The OpenSSF Package Analysis project identified 'dex-creator' @ 2.0.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 dex-creator are malicious?

The following npm versions of dex-creator are flagged malicious: 1.0.1, 1.0.2, 2.0.0. Treat any of these as compromised.

How do I remediate dex-creator if I installed it?

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

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

Yes — dex-creator is associated with the RLMA-2025-05722, RLUA-2026-01242 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 dex-creator 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 dex-creator (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dex-creator across your stack and pipelines.

Malicious package

dex-creatornpm

dex-creator is a confirmed malicious npm package (MAL-2025-47582) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dex-creator (npm)

MAL-2025-47582

Immediate action

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

npm uninstall dex-creator

What this malware does

The package communicates with a domain associated with malicious activity.

The OpenSSF Package Analysis project identified 'dex-creator' @ 2.0.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

3 flagged

1.0.11.0.22.0.0

Indicators of compromise (SHA-256)

a45a7bed266fa05cf91945ed835fdf225abff89dd8dcde90c90dc769b04e15e3

56f740c9e4fd7fb0e2ae4af71e33de73c34606d7bb52052a6fb795e114128362

bd1ed548342196caadca2622715232d4e13457c82af0ba422276f1058d2834a4

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 dex-creator (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dex-creator across your stack and pipelines.
If you installed it — respond
Remove dex-creator 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 dex-creator 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 dex-creator 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. dex-creator on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05722RLUA-2026-01242

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks dex-creator-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