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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

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.

Can O3 Security detect lab-services in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking lab-services and packages like it before any post-install script runs.

Malicious package

lab-servicesnpm

Malicious code in lab-services (npm) Remove it immediately and rotate any exposed credentials.

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

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

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection