Which versions of @phonos/types are malicious?

Every published version of @phonos/types on npm is considered malicious. Remove the package entirely.

How do I remediate @phonos/types if I installed it?

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

If @phonos/types 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.

How do I find @phonos/types across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @phonos/types (all published versions).

Malicious package

@phonos/typesnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

@phonos/types is a confirmed malicious npm package (MAL-2026-2409) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @phonos/types (npm)

MAL-2026-2409

Immediate action

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

npm uninstall @phonos/types

What this malware does

Multiple evidences indicate malicious behavior: obfuscation, suspicious install script, access to sensitive functionalities, and untrustworthy source.

The package @phonos/types was found to contain malicious code.

Malicious versions

all versions

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

Indicators of compromise (SHA-256)

e8c10ea271203f85e595559214b08565cef54710fcc605eca02483606041cf51

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @phonos/types (all published versions).
If you installed it — respond
Remove @phonos/types 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 @phonos/types 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. @phonos/types 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.

References

app.safedep.io

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @phonos/types-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