Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @taktikangea published 103 malicious packages. See the full campaign →
Malicious package

@taktikangea/architecto-cumque-doloribusnpm

Advisory published Updated

@taktikangea/architecto-cumque-doloribus is a confirmed malicious npm package (MAL-2025-9399) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @taktikangea/architecto-cumque-doloribus (npm)

MAL-2025-9399
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @taktikangea/architecto-cumque-doloribus

What this malware does

The package @taktikangea/architecto-cumque-doloribus was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @taktikangea/architecto-cumque-doloribus (all published versions).

  2. If you installed it — respond

    Remove @taktikangea/architecto-cumque-doloribus 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.

  3. Did it already run?

    If @taktikangea/architecto-cumque-doloribus 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. @taktikangea/architecto-cumque-doloribus on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @taktikangea/architecto-cumque-doloribus-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.

Explore

@taktikangea/architecto-cumque-doloribus (npm) malicious package — MAL-2025-9399 | O3 Security