Which versions of @frontembed/testtest are malicious?

The following npm versions of @frontembed/testtest are flagged malicious: 99.99.100. Treat any of these as compromised.

How do I remediate @frontembed/testtest if I installed it?

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

If @frontembed/testtest 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 @frontembed/testtest part of a known attack campaign?

Yes — @frontembed/testtest is associated with the RLMA-2026-04723, RLUA-2026-05866 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 @frontembed/testtest across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @frontembed/testtest (version 99.99.100).

Malicious package

@frontembed/testtestnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@frontembed/testtest is a confirmed malicious npm package (MAL-2026-7070) that executes malicious code on install (malicious version 99.99.100). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @frontembed/testtest (npm)

MAL-2026-7070

Immediate action

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

npm uninstall @frontembed/testtest

Malicious versions

1 flagged

99.99.100

Indicators of compromise (SHA-256)

de5a26fe4e4765b3128744b9bc9cf907246e4b4d474cc78c84b9d4d489029b4f

f90d9b90ba4d568ea36a719de637933cad3f7d08fc8025c1ba8bad8ab4a242b1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04723RLUA-2026-05866

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @frontembed/testtest-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