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

@teamteanpm2024/quas-provident-temporenpm

Advisory published Updated

@teamteanpm2024/quas-provident-tempore is a confirmed malicious npm package (MAL-2025-9543) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @teamteanpm2024/quas-provident-tempore (npm)

MAL-2025-9543
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @teamteanpm2024/quas-provident-tempore

What this malware does

The package @teamteanpm2024/quas-provident-tempore 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 @teamteanpm2024/quas-provident-tempore (all published versions).

  2. If you installed it — respond

    Remove @teamteanpm2024/quas-provident-tempore 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 @teamteanpm2024/quas-provident-tempore 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. @teamteanpm2024/quas-provident-tempore 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 @teamteanpm2024/quas-provident-tempore-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
@teamteanpm2024/quas-provident-tempore (npm) malicious package — MAL-2025-9543 | O3 Security