How do I remediate ddddddd1d if I installed it?

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

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

Yes — ddddddd1d is associated with the RLMA-2026-01238 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 ddddddd1d across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ddddddd1d (73 malicious versions).

Malicious package

ddddddd1dnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

ddddddd1d is a confirmed malicious npm package (MAL-2026-1706) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ddddddd1d (npm)

MAL-2026-1706

Immediate action

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

npm uninstall ddddddd1d

What this malware does

The package ddddddd1d was found to contain malicious code.

Malicious versions

73 flagged

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.71.0.81.0.91.0.101.0.111.0.121.0.131.0.141.0.151.0.171.0.181.0.191.0.221.0.231.0.241.0.251.0.261.0.271.0.281.0.291.0.301.0.311.0.321.0.331.0.341.0.351.0.361.0.371.0.381.0.391.0.401.0.411.0.421.0.431.0.441.0.451.0.461.0.471.0.481.0.491.0.501.0.511.0.521.0.531.0.541.0.551.0.561.0.571.0.581.0.591.0.601.0.611.0.621.0.641.0.651.0.661.0.671.0.681.0.691.0.701.0.711.0.721.0.731.0.741.0.751.0.76

Indicators of compromise (SHA-256)

d71ee6cec2b26384c338e49483c8f011ef7ad32b03deae100582c6ed978cdeb0

2b26bb490eddaee9c3130c572772252e4959e395be8f786d04e125aed7f6c9da

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ddddddd1d (73 malicious versions).
If you installed it — respond
Remove ddddddd1d 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 ddddddd1d 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. ddddddd1d on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, and 65 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01238

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ddddddd1d-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