Which versions of tdangularjs are malicious?

The following npm versions of tdangularjs are flagged malicious: 1.0.0, 8.7.6. Treat any of these as compromised.

How do I remediate tdangularjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for tdangularjs (2 malicious versions).

Malicious package

tdangularjsnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

tdangularjs is a confirmed malicious npm package (MAL-2026-1860) that executes malicious code on install (malicious versions 1.0.0, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tdangularjs (npm)

MAL-2026-1860

Immediate action

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

npm uninstall tdangularjs

What this malware does

The package tdangularjs was found to contain malicious code.

Malicious versions

2 flagged

1.0.08.7.6

Indicators of compromise (SHA-256)

9b2bb7354768883beb4c6c89b8af49d0c358aa4ec9d6849633310180d65ebc66

6e881cda0104897acf333fb57eceef4ac9b4b542ce79cb33e5956670cd1763ec

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01608

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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