Which versions of @examplecorptest/hearsay-design-system-test are malicious?

The following npm versions of @examplecorptest/hearsay-design-system-test are flagged malicious: 9.5.0. Treat any of these as compromised.

How do I remediate @examplecorptest/hearsay-design-system-test if I installed it?

Remove @examplecorptest/hearsay-design-system-test 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 @examplecorptest/hearsay-design-system-test — how do I know if it already compromised me?

If @examplecorptest/hearsay-design-system-test 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 @examplecorptest/hearsay-design-system-test part of a known attack campaign?

Yes — @examplecorptest/hearsay-design-system-test is associated with the RLMA-2026-05422, RLUA-2026-05864 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 @examplecorptest/hearsay-design-system-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @examplecorptest/hearsay-design-system-test (version 9.5.0).

Malicious package

@examplecorptest/hearsay-design-system-testnpm

Advisory published Jul 20, 2026Updated Sep 1, 2026

@examplecorptest/hearsay-design-system-test is a confirmed malicious npm package (MAL-2026-10880) that executes malicious code on install (malicious version 9.5.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @examplecorptest/hearsay-design-system-test (npm)

MAL-2026-10880

Immediate action

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

npm uninstall @examplecorptest/hearsay-design-system-test

Malicious versions

1 flagged

9.5.0

Indicators of compromise (SHA-256)

30a5a694624f9877e11d96177bc3c847910fd215169b51f91611df9274a8cb47

7d2442e723647757c67c40028b6764d5b17c8056948c360f9feefa76cef6a295

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05422RLUA-2026-05864

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @examplecorptest/hearsay-design-system-test-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