Which versions of @tc-core/member-service are malicious?

The following npm versions of @tc-core/member-service are flagged malicious: 0.0.0-defensive-callback. Treat any of these as compromised.

How do I remediate @tc-core/member-service if I installed it?

Remove @tc-core/member-service 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 @tc-core/member-service — how do I know if it already compromised me?

If @tc-core/member-service 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 @tc-core/member-service part of a known attack campaign?

Yes — @tc-core/member-service is associated with the RLMA-2026-04787, RLUA-2026-05932 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 @tc-core/member-service across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @tc-core/member-service (version 0.0.0-defensive-callback).

Malicious package

@tc-core/member-servicenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@tc-core/member-service is a confirmed malicious npm package (MAL-2026-7094) that executes malicious code on install (malicious version 0.0.0-defensive-callback). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @tc-core/member-service (npm)

MAL-2026-7094

Immediate action

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

npm uninstall @tc-core/member-service

Malicious versions

1 flagged

0.0.0-defensive-callback

Indicators of compromise (SHA-256)

8e66da4346795b2005a6d0e86c335cc5fb730fba33c96c81028d6ac790c1a41b

6ed669cdfdf756bec9abae03fe4b73774915c46d64d9fcd53b858b57d9e684d6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04787RLUA-2026-05932

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @tc-core/member-service-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