Which versions of my-empty-package are malicious?

The following npm versions of my-empty-package are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate my-empty-package if I installed it?

Remove my-empty-package 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.

I already installed my-empty-package — how do I know if it already compromised me?

If my-empty-package 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 my-empty-package part of a known attack campaign?

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

Malicious package

my-empty-packagenpm

Malicious code in my-empty-package (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10535

Immediate action

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

npm uninstall my-empty-package

What this malware does

package.json declares postinstall: node index.js. On npm install, index.js branches on os.platform() and executes platform-specific shell commands: osascript on macOS, powershell -WindowStyle Hidden -EncodedCommand <base64-UTF16LE> on Windows, and python3 -c 'os.system(...)' on Linux. After the payload runs, a cleanup step renames a shipped package.md over package.json and unlinks index.js itself, removing the install-time script from disk and presenting a different manifest to any post-install inspection. The hidden-window base64-encoded PowerShell invocation is a standard malware evasion technique. Manifest swap + entrypoint self-deletion is anti-forensic behavior with no legitimate purpose. Even though the current payload body is a benign demonstration (opens the calculator), the delivery framework is a fully-functional install-time RCE dropper skeleton: any content placed in the platform branches would execute automatically on install with the user's privileges and then erase its own traces.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

914ffc98ce1f6553e4f9655208318800d0d22663842eb4c9a3d0d51d4f143bdd

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for my-empty-package (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging my-empty-package across your stack and pipelines.
If you installed it — respond
Remove my-empty-package 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.
Did it already run?
If my-empty-package 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 my-empty-package 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. my-empty-package 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-010388

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks my-empty-package-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.

Malware detection Runtime egress monitoring