Which versions of bulk-add-sdk are malicious?

The following npm versions of bulk-add-sdk are flagged malicious: 1.99.99. Treat any of these as compromised.

How do I remediate bulk-add-sdk if I installed it?

bulk-add-sdk establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed bulk-add-sdk — how do I know if it already compromised me?

If bulk-add-sdk 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 bulk-add-sdk part of a known attack campaign?

Yes — bulk-add-sdk is associated with the IN-MAL-2026-020225 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 bulk-add-sdk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bulk-add-sdk (version 1.99.99).

Malicious package

bulk-add-sdknpm

Advisory published Sep 21, 2026Updated Sep 21, 2026

bulk-add-sdk is a confirmed malicious npm package (MAL-2026-16325) that opens a backdoor for remote access (malicious version 1.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bulk-add-sdk (npm)

MAL-2026-16325

Immediate action

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

npm uninstall bulk-add-sdk

What this malware does

Package declares scripts.install: "node extract.js thd-orangepay", causing extract.js to run automatically on npm install. The script collects hostname, platform, arch, cwd, and the machine's public IP (obtained by shelling out via execSync to curl -s ifconfig.me || wget...) and transmits the data to a hardcoded subdomain of wallclip.me over two channels: an HTTPS POST via https.request with rejectUnauthorized: false (disabling certificate verification), and a DNS lookup against a beacon of the form ${project_id}.${safeHost}.[...].wallclip.me so a passive DNS observer receives the hostname and project identifier even when outbound TCP/443 is blocked. The package main entry is a stub with no library functionality, so the install-time beacon is the package's sole effect. The package name resembles a legitimate SDK but ships only a reconnaissance beacon targeting a non-first-party domain.

Malicious versions

1 flagged

1.99.99

Indicators of compromise (SHA-256)

b131d84c624f7eb89d720ed0ec1435eef5f5f9ff800d1cef88b20c18c7374023

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for bulk-add-sdk (version 1.99.99).
If you installed it — respond
bulk-add-sdk establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bulk-add-sdk 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. bulk-add-sdk on npm has been identified as a malicious package (version 1.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020225

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bulk-add-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database