Which versions of @achuthvp/postinstall-poc are malicious?

The following npm versions of @achuthvp/postinstall-poc are flagged malicious: 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate @achuthvp/postinstall-poc if I installed it?

@achuthvp/postinstall-poc 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 @achuthvp/postinstall-poc — how do I know if it already compromised me?

If @achuthvp/postinstall-poc 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 @achuthvp/postinstall-poc part of a known attack campaign?

Yes — @achuthvp/postinstall-poc is associated with the IN-MAL-2026-006379, IN-MAL-2026-006381, IN-MAL-2026-006378, IN-MAL-2026-006380 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 @achuthvp/postinstall-poc 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 @achuthvp/postinstall-poc (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @achuthvp/postinstall-poc across your stack and pipelines.

Malicious package

@achuthvp/postinstall-pocnpm

Malicious code in @achuthvp/postinstall-poc (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5741

Immediate action

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

npm uninstall @achuthvp/postinstall-poc

What this malware does

package.json declares scripts.postinstall = node postinstall.js. On every npm install, postinstall.js runs execSync('id') and POSTs a JSON body containing the id output, os.hostname(), platform, architecture, process.cwd(), and Node version to the hardcoded URL https://webhook.site/fceebb0d-9f11-4ac0-98db-6f6b3925f7d3 (postinstall.js line 14, exfil call constructed via https.request at line 21 with POST at line 24). The behavior is unconditional, undisclosed in the README (Does nothing much), and fires on a default install. Although the package self-describes as a POC, the install-time mechanism is identical to an active reconnaissance/exfiltration payload: any developer or CI machine installing this package leaks its identity (uid/gid/groups via id, hostname, cwd, platform) to an attacker-readable webhook bin.

Malicious versions

2 flagged

1.0.21.0.3

Indicators of compromise (SHA-256)

8a5c98a52f068d49b6fbdf96d76a24df1f7807c41e53ab75d6270ca0ce64fb1a

91e690492c565ad314bb15d92061ec65f0f5a6622e3b20d9c4acf3170df13ac5

972fb1c4637e2b6b3d0ed4a3d24b0f5a91fe190baf271328278eb756c9611e36

c3dc0d7b5fc216ae117dda9c492a6bbdff46e49ab53f069c2d525dab001bcdb9

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-006379IN-MAL-2026-006381IN-MAL-2026-006378IN-MAL-2026-006380

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @achuthvp/postinstall-poc-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