Which versions of lab-services are malicious?

The following npm versions of lab-services are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate lab-services if I installed it?

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

If lab-services 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 lab-services part of a known attack campaign?

Yes — lab-services is associated with the IN-MAL-2026-006913 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 lab-services across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lab-services (version 99.0.0).

Malicious package

lab-servicesnpm

Advisory published Jun 17, 2026Updated Jun 17, 2026

lab-services is a confirmed malicious npm package (MAL-2026-6065) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lab-services (npm)

MAL-2026-6065

Immediate action

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

npm uninstall lab-services

What this malware does

On npm install, the package's preinstall lifecycle script (node.js) collects host identifiers from the installing machine — hostname, public IP (resolved via api.ipify.org), current working directory, OS platform, and architecture — and POSTs them to a hardcoded Discord webhook at discord.com/api/webhooks/1516798168304586833/. The behavior fires automatically with no opt-in and no user interaction. The package is published at version 99.0.0 with a description self-identifying as an 'Authorized Security Research PoC - Dependency Confusion Assessment' and keywords including 'bugbounty', 'msrc', 'security-holding' — the structural shape of a dependency-confusion squat against an internal package name of the same identifier. Regardless of researcher intent, the public publication causes any installer who resolves this name (including unrelated organizations or accidental typo-installs) to leak internal network metadata to a third-party webhook.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

4acaa72e3c14b79785540c878cb48f7a0cdc238d20ac9cebd6ffdd42061f6e7b

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-006913

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks lab-services-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