Which versions of delta-time-32bb are malicious?

The following npm versions of delta-time-32bb are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate delta-time-32bb if I installed it?

delta-time-32bb 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 delta-time-32bb — how do I know if it already compromised me?

If delta-time-32bb 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 delta-time-32bb part of a known attack campaign?

Yes — delta-time-32bb is associated with the IN-MAL-2026-007391 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 delta-time-32bb across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for delta-time-32bb (version 1.0.0).

Malicious package

delta-time-32bbnpm

Advisory published Jun 23, 2026Updated Jun 23, 2026

delta-time-32bb is a confirmed malicious npm package (MAL-2026-6351) 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 delta-time-32bb (npm)

MAL-2026-6351

Immediate action

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

npm uninstall delta-time-32bb

What this malware does

Package declares a postinstall hook ("postinstall": "node run.js" in package.json) that executes run.js automatically on npm install. run.js imports os, fs, http, https, and child_process and collects host identifiers and environment data — os.hostname(), os.userInfo(), os.platform(), process.env.USER, process.cwd() — base64-encodes the payload via Buffer.from(...).toString('base64'), and POSTs over http/https. The package has no documented purpose justifying install-time host reconnaissance and outbound network. The shape (lifecycle-triggered collection of host identity + environment + base64 wrapping + HTTP POST) is a credential/host-recon exfiltration beacon executed without user interaction on default install.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bcbd5b3b8f7702c8cf59c094e98f078f68563d407235bce1dd0ec6e6522fe03b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for delta-time-32bb (version 1.0.0).
If you installed it — respond
delta-time-32bb 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 delta-time-32bb 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. delta-time-32bb 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-007391

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks delta-time-32bb-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