Which versions of @uniqa/user-account-spec-api are malicious?

The following npm versions of @uniqa/user-account-spec-api are flagged malicious: 77.77.77. Treat any of these as compromised.

How do I remediate @uniqa/user-account-spec-api if I installed it?

Remove @uniqa/user-account-spec-api 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 @uniqa/user-account-spec-api — how do I know if it already compromised me?

If @uniqa/user-account-spec-api 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 @uniqa/user-account-spec-api part of a known attack campaign?

Yes — @uniqa/user-account-spec-api is associated with the RLMA-2025-01292 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 @uniqa/user-account-spec-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @uniqa/user-account-spec-api (version 77.77.77).

Part of a larger attack: @uniqa published 19 malicious packages. See the full campaign →

Malicious package

@uniqa/user-account-spec-apinpm

Advisory published Mar 28, 2025Updated Mar 28, 2025

@uniqa/user-account-spec-api is a confirmed malicious npm package (MAL-2025-2828) that executes malicious code on install (malicious version 77.77.77). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @uniqa/user-account-spec-api (npm)

MAL-2025-2828

Immediate action

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

npm uninstall @uniqa/user-account-spec-api

Malicious versions

1 flagged

77.77.77

Indicators of compromise (SHA-256)

d796de6fa58bd94ed8b8827a9ac99cf978b171057f52d60d86d599ff17735d2e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @uniqa/user-account-spec-api (version 77.77.77).
If you installed it — respond
Remove @uniqa/user-account-spec-api 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 @uniqa/user-account-spec-api 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. @uniqa/user-account-spec-api on npm has been identified as a malicious package (version 77.77.77 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01292

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @uniqa/user-account-spec-api-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