Which versions of simplenewnpmpackage are malicious?

The following npm versions of simplenewnpmpackage are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate simplenewnpmpackage if I installed it?

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

If simplenewnpmpackage was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is simplenewnpmpackage part of a known attack campaign?

Yes — simplenewnpmpackage is associated with the IN-MAL-2026-020493 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 simplenewnpmpackage across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for simplenewnpmpackage (version 1.0.2).

Malicious package

simplenewnpmpackagenpm

Advisory published Sep 23, 2026Updated Sep 23, 2026

simplenewnpmpackage is a confirmed malicious npm package (MAL-2026-16479) that opens a backdoor for remote access (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in simplenewnpmpackage (npm)

MAL-2026-16479

Immediate action

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

npm uninstall simplenewnpmpackage

What this malware does

On require/import, index.js issues an HTTPS GET to a hardcoded interactsh OAST subdomain (dapnhid534ch06s9vpm0mbg1httu5gytc.oast.fun) with the installer's os.platform() and os.hostname() as query parameters. The package ships no other functionality; its main module exists solely to fire this out-of-band beacon on load. oast.fun is a public out-of-band interaction collector used to receive callbacks from targets, and the hardcoded subdomain is bound to a specific listener controlled by whoever published the package. This is the canonical dependency-confusion / namesquat probe pattern, in which a package is published to catch internal-name mis-resolutions and report back the host that installed it.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

76315a0ce965c3a1f5b6342caa9d9ce8db4b341b641b2dbb696ebd52bd6149ec

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for simplenewnpmpackage (version 1.0.2).
If you installed it — respond
simplenewnpmpackage 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 simplenewnpmpackage was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-020493

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks simplenewnpmpackage-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