Which versions of serverless-twi-testing are malicious?

The following npm versions of serverless-twi-testing are flagged malicious: 1.0.7. Treat any of these as compromised.

How do I remediate serverless-twi-testing if I installed it?

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

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

Yes — serverless-twi-testing is associated with the RLMA-2026-05312, RLUA-2026-06485 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 serverless-twi-testing across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for serverless-twi-testing (version 1.0.7).

Malicious package

serverless-twi-testingnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

serverless-twi-testing is a confirmed malicious npm package (MAL-2026-7418) that executes malicious code on install (malicious version 1.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in serverless-twi-testing (npm)

MAL-2026-7418

Immediate action

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

npm uninstall serverless-twi-testing

Malicious versions

1 flagged

1.0.7

Indicators of compromise (SHA-256)

25bfcaa55173de70b0aa67ed1757c3aecc3ec2834ecb079a4f079ea0a34d90af

c36edc4fd38df66ab79d13eb5b53ac806d6c3a7f5f0349941b80bc1f356c8de8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05312RLUA-2026-06485

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks serverless-twi-testing-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