Which versions of subapp-pkg-util are malicious?

The following npm versions of subapp-pkg-util are flagged malicious: 99.0.1. Treat any of these as compromised.

How do I remediate subapp-pkg-util if I installed it?

subapp-pkg-util 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 subapp-pkg-util — how do I know if it already compromised me?

If subapp-pkg-util 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 subapp-pkg-util part of a known attack campaign?

Yes — subapp-pkg-util is associated with the IN-MAL-2026-011088 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 subapp-pkg-util 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 subapp-pkg-util (version 99.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging subapp-pkg-util across your stack and pipelines.

Malicious package

subapp-pkg-utilnpm

subapp-pkg-util is a confirmed malicious npm package (MAL-2026-11045) that opens a backdoor for remote access (malicious version 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in subapp-pkg-util (npm)

MAL-2026-11045

Immediate action

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

npm uninstall subapp-pkg-util

What this malware does

package.json declares a postinstall hook that runs index.js on npm install. index.js collects host identifiers (os.hostname(), os.userInfo(), os.platform(), OS release) and enriches them with public IP (via ipify) and geo/ISP (via ipapi.co), then POSTs the JSON payload to a hardcoded Burp Collaborator subdomain at https://dq7q2vt6l79ouvgyzavan3w2rtxkp8gw5.oastify.com/callback. The package self-describes as a dependency-confusion takeover PoC; the beacon fires automatically on install without user interaction.

The OpenSSF Package Analysis project identified 'subapp-pkg-util' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.0.1

Indicators of compromise (SHA-256)

9ec05191ebd2f02dcf912c49fc5d345c3b9201fb691a11a0142fec91cc6d42d4

ae51b43e9a5110ec02eb9aa1cbf03837b2a560f4b6c8168b1c2d675802a113ae

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 subapp-pkg-util (version 99.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging subapp-pkg-util across your stack and pipelines.
If you installed it — respond
subapp-pkg-util 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 subapp-pkg-util 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 subapp-pkg-util 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. subapp-pkg-util on npm has been identified as a malicious package (version 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011088

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks subapp-pkg-util-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