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

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

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

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

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

Yes — @larocas-bbresearch/tp-probe-dc7a3670 is associated with the RLMA-2026-10641 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-dc7a3670 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @larocas-bbresearch/tp-probe-dc7a3670 (version 1.0.0).

Malicious package

@larocas-bbresearch/tp-probe-dc7a3670npm

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

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

MAL-2026-16528

Immediate action

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

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

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7629aa3e67ecb5911e79b48b2a8ca35c215656982b16a1d5a9f10555d24635ee

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-10641

Credits

ReversingLabs · finder

Detect & block this

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