Which versions of field-plus are malicious?

The following npm versions of field-plus are flagged malicious: 99.99.1, 99.99.2. Treat any of these as compromised.

How do I remediate field-plus if I installed it?

field-plus 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 field-plus — how do I know if it already compromised me?

If field-plus 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.

Is field-plus part of a known attack campaign?

Yes — field-plus is associated with the IN-MAL-2026-006492, IN-MAL-2026-006493, GHSA-wcq8-7m2v-8r69 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 field-plus across my projects, lockfiles, and CI pipelines?

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

Malicious package

field-plusnpm

field-plus is a confirmed malicious npm package (MAL-2026-5777) that opens a backdoor for remote access (malicious versions 99.99.1, 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in field-plus (npm)

MAL-2026-5777

Immediate action

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

npm uninstall field-plus

What this malware does

package.json declares both preinstall and postinstall scripts that run curl against a hardcoded bare-IP HTTP endpoint (http://3.7.226.146:9000/callback), sending the installer's username ($(whoami)), hostname ($(hostname)), current working directory ($(pwd)), and a timestamp as query-string parameters. Output is suppressed and errors swallowed with || true so the beacon stays silent during npm install. The tarball ships only package.json — main: index.js is declared but not present — so the package has no library functionality; its sole effect on installation is the identity beacon. Version 99.99.1 plus the description "testing field plus" is the canonical shape of a dependency-confusion / namespace-squat probe used to identify which organizations resolve an internal-named package from the public registry.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

99.99.199.99.2

Indicators of compromise (SHA-256)

0112dc4801bb261e86a2f68d5fd49b6c955bb4e82f872c72e61e49cc638ca91c

da1412d0ba61cadb9c28005b754fac70658159c6671eb92bb66bcc5ffa43d285

b9c01dfacc7ff1df16b13ba67ffe0c3ac7ff2e533c1d44bd3d402736814f3656

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for field-plus (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging field-plus across your stack and pipelines.
If you installed it — respond
field-plus 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 field-plus 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.
How O3 protects you
O3 blocks field-plus 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. field-plus on npm has been identified as a malicious package (versions 99.99.1, 99.99.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006492IN-MAL-2026-006493GHSA-wcq8-7m2v-8r69

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks field-plus-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