Which versions of dwagger-express-router are malicious?

The following npm versions of dwagger-express-router are flagged malicious: 1.1.2, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate dwagger-express-router if I installed it?

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

If dwagger-express-router 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 dwagger-express-router part of a known attack campaign?

Yes — dwagger-express-router is associated with the RLMA-2026-05043, RLUA-2026-06180 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 dwagger-express-router across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dwagger-express-router (3 malicious versions).

Malicious package

dwagger-express-routernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

dwagger-express-router is a confirmed malicious npm package (MAL-2026-7254) that executes malicious code on install (malicious versions 1.1.2, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dwagger-express-router (npm)

MAL-2026-7254

Immediate action

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

npm uninstall dwagger-express-router

Malicious versions

3 flagged

1.1.21.1.48.7.6

Indicators of compromise (SHA-256)

6a17680a6cae87d2f3e1497c7532c4d6683e2bfa64cdeca47d65a2a1e0274853

f8b0a156dcd4238bf7ae5648dd96d1d5b318e9fbdaaeba38f6a671da1ec11d51

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dwagger-express-router (3 malicious versions).
If you installed it — respond
Remove dwagger-express-router 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 dwagger-express-router 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. dwagger-express-router on npm has been identified as a malicious package (versions 1.1.2, 1.1.4, 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05043RLUA-2026-06180

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks dwagger-express-router-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