Which versions of swnwall are malicious?

The following npm versions of swnwall are flagged malicious: 1.2.10. Treat any of these as compromised.

How do I remediate swnwall if I installed it?

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

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

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

Malicious package

swnwallnpm

swnwall is a confirmed malicious npm package (MAL-2026-16211) that executes malicious code on install (malicious version 1.2.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in swnwall (npm)

MAL-2026-16211

Immediate action

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

npm uninstall swnwall

What this malware does

On require/import, index.js invokes initialize() which spawns loader.js as a detached, hidden background child process (detached: true, windowsHide: true, stdio: 'ignore', unref'd) and records a.pid file to avoid re-spawning. loader.js performs an HTTPS GET against https://api.npoint.io/641d37178a880b1e8b8f (a user-editable JSON hosting service), base64-decodes the code field of the response, and executes the decoded payload via new Function("require",..., decodedCode)(require, __dirname, __filename,...), granting the fetched code full access to Node's require, filesystem, and process APIs on the installer's machine. loader.js additionally monkey-patches Module.prototype.require to force windowsHide on all child_process spawn calls and reroute execSync through a hidden cmd.exe /c, concealing further child-process activity. The remote payload is mutable and attacker-controllable via the npoint.io endpoint.

Malicious versions

1 flagged

1.2.10

Indicators of compromise (SHA-256)

70fb3b7b76f32b1c101b04c15933b403658f199267e9c3c34ebea9aba917949a

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

Campaign

IN-MAL-2026-020075

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database