Which versions of @larocas-bbresearch/tp-probe-e29834ce are malicious?

The following npm versions of @larocas-bbresearch/tp-probe-e29834ce are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @larocas-bbresearch/tp-probe-e29834ce if I installed it?

Remove @larocas-bbresearch/tp-probe-e29834ce 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 @larocas-bbresearch/tp-probe-e29834ce — how do I know if it already compromised me?

If @larocas-bbresearch/tp-probe-e29834ce 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 @larocas-bbresearch/tp-probe-e29834ce part of a known attack campaign?

Yes — @larocas-bbresearch/tp-probe-e29834ce is associated with the RLMA-2026-10642, IN-MAL-2026-020767, IN-MAL-2026-020769 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 @larocas-bbresearch/tp-probe-e29834ce across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @larocas-bbresearch/tp-probe-e29834ce (2 malicious versions).

Malicious package

@larocas-bbresearch/tp-probe-e29834cenpm

Advisory published Sep 22, 2026Updated Sep 30, 2026

@larocas-bbresearch/tp-probe-e29834ce is a confirmed malicious npm package (MAL-2026-16529) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @larocas-bbresearch/tp-probe-e29834ce (npm)

MAL-2026-16529

Immediate action

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

npm uninstall @larocas-bbresearch/tp-probe-e29834ce

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

90856b8237135657ff40e0a22828cf26306137dfe28a3339180bc8fb90916c98

7279432ffb7dc233307df869ac5faaded0fef16333ec8a5948b15bae7bd716a7

9dc677d00157dddc1ef9b7e4a9de0a092a1515cef1268eedbe4ee1b44203ebca

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @larocas-bbresearch/tp-probe-e29834ce (2 malicious versions).
If you installed it — respond
Remove @larocas-bbresearch/tp-probe-e29834ce 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 @larocas-bbresearch/tp-probe-e29834ce 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. @larocas-bbresearch/tp-probe-e29834ce on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-10642IN-MAL-2026-020767IN-MAL-2026-020769

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @larocas-bbresearch/tp-probe-e29834ce-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