Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

fieldbase-webapplication-buildtoolsnpm

fieldbase-webapplication-buildtools is a confirmed malicious npm package (MAL-2026-15847) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fieldbase-webapplication-buildtools (npm)

MAL-2026-15847
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall fieldbase-webapplication-buildtools

What this malware does

package.json declares preinstall and install lifecycle scripts that collect the installer's username (whoami), hostname, current working directory, and npm package name, base64-encode them, and send them to the hardcoded endpoint https://eoy34oyrep9j5x8.m.pipedream.net via both an HTTPS GET path and a DNS-lookup channel (nslookup against a subdomain of the same host). This fires automatically on npm install with no user interaction. The version number 99.99.99 and package name pattern are consistent with a dependency-confusion lure targeting an internal package name.

The OpenSSF Package Analysis project identified 'fieldbase-webapplication-buildtools' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
99.99.99

Indicators of compromise (SHA-256)

2429684480958b2faee9e5dc817ba4f9b5c9e00bd73052546dde0c033654e8ba
8c30b72acbc526ba924e071ebefd3bc3a131d6dc29abaa71fa76deab2836345e

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fieldbase-webapplication-buildtools (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fieldbase-webapplication-buildtools across your stack and pipelines.

  2. If you installed it — respond

    Remove fieldbase-webapplication-buildtools 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.

  3. Did it already run?

    If fieldbase-webapplication-buildtools was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks fieldbase-webapplication-buildtools before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. fieldbase-webapplication-buildtools on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019382

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks fieldbase-webapplication-buildtools-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.

Explore