Which versions of seaport-core-16 are malicious?

Every published version of seaport-core-16 on npm is considered malicious. Remove the package entirely.

How do I remediate seaport-core-16 if I installed it?

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

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

Yes — seaport-core-16 is associated with the GHSA-xwxq-h8q6-2494 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 seaport-core-16 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for seaport-core-16 (all published versions).

Malicious package

seaport-core-16npm

Advisory published Apr 13, 2026Updated Apr 23, 2026

seaport-core-16 is a confirmed malicious npm package (MAL-2026-2636) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in seaport-core-16 (npm)

MAL-2026-2636

Immediate action

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

npm uninstall seaport-core-16

What this malware does

Package exfiltrates user info to a remote server via wget in test, preinstall, and preupdate scripts. Very few published versions.

The package seaport-core-16 was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

dd2d69fe2df28a03c312583b336306983aa535490c7ccfc0e1ba2d5dd061559d

be2cd9e6e61b20566214a0627d5923ec7cbe799e9757d25fd883f46616e5b58b

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for seaport-core-16 (all published versions).
If you installed it — respond
seaport-core-16 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 seaport-core-16 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. seaport-core-16 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xwxq-h8q6-2494

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks seaport-core-16-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

Explore

All malware advisories How O3 detects malware Vulnerability database