Which versions of bigbob22-test are malicious?

The following npm versions of bigbob22-test are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate bigbob22-test if I installed it?

bigbob22-test is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed bigbob22-test — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for bigbob22-test (version 1.0.0).

Malicious package

bigbob22-testnpm

Advisory published Nov 1, 2026Updated Nov 2, 2026

bigbob22-test is a confirmed malicious npm package (MAL-2026-18457) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bigbob22-test (npm)

MAL-2026-18457

Immediate action

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

npm uninstall bigbob22-test

What this malware does

[email protected] has no functional code and an empty README. Its preinstall script runs node preinstall.js on npm install, which POSTs the machine's hostname, the OS username and the local time to the Discord webhook https://canary.discord.com/api/webhooks/1566232728179843243/pM5rDIrCRrEpQRbA7ibaiQk1XOQlIftmBacA5s8jD8NvXn5W-rS832DOWHQS-G-j3N6U as "PC Notifier". It was published by the npm account cutekitten05, which used the same script in wallet-adapter-base, axelarjs-sdk, cutekitten-test and sol-wallet-adapter on 2026-11-01.

The package's npm preinstall lifecycle script (preinstall.js) runs automatically on npm install and transmits installer-side identifiers to an attacker-controlled endpoint. On line 23 it reads os.hostname() and os.userInfo().username, composes a message including those values, and on line 33 POSTs the payload to a hardcoded Discord webhook at https://canary.discord.com/api/webhooks/1566232728179843243/.... The destination is a Discord webhook (not the package publisher's infrastructure), the behavior is undocumented, and no opt-out is provided. Installing this package causes host and user identity information to be sent to a third-party endpoint controlled by whoever created the webhook.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

124d3c6d5bdd1012a98468100194204703d1da8b6ba77322b9b1ea035b04c55c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for bigbob22-test (version 1.0.0).
If you installed it — respond
bigbob22-test is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bigbob22-test 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. bigbob22-test 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

IN-MAL-2026-022485

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

O3 blocks bigbob22-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database