Which versions of sixseven1 are malicious?

The following npm versions of sixseven1 are flagged malicious: 1.1.7, 1.7.7, 2.0.0. Treat any of these as compromised.

How do I remediate sixseven1 if I installed it?

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

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

Yes — sixseven1 is associated with the GHSA-753r-q78v-8775, IN-MAL-2026-010196, IN-MAL-2026-010195, IN-MAL-2026-010194 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 sixseven1 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 sixseven1 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sixseven1 across your stack and pipelines.

Malicious package

sixseven1npm

Malicious code in sixseven1 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10372

Immediate action

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

npm uninstall sixseven1

What this malware does

The package declares no install/postinstall/preinstall lifecycle scripts, and its declared main is sw.js — a browser ServiceWorker that uses importScripts, self.addEventListener('install'|'fetch'|'activate'), and self.clients.claim(). Loading it in Node via require() would throw on the browser-only globals before any code ran, so installing this package does not execute any of the bundled assets on a developer's machine. The tarball ships a static 'web unblocker' proxy site (HTML masquerading as 'Riverbend Tutoring' that injects a popunder to https://abdct.com on user click, plus the ServiceWorker that proxies cross-origin fetches and rewrites HTML), along with multiple heavily obfuscated JS bundles under assets/ (e.g. assets/3oruu3por5.js, assets/blhj60cfaf.js, etc.) consistent with that proxy site rather than with a Node library. A bundled auto-publish.sh enumerates a sequential family of package names (sixseven1..sixseven10), indicating this publish is part of a name-squat batch on the npm registry. Risk to anyone running npm install sixseven9 is limited to disk usage and registry pollution; the obfuscated assets and ad popunder only affect end users of a hypothetical site that deploys this code, not developers who install the package. Routing to human review so the registry can decide whether to remove the squat batch.

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

3 flagged

1.1.71.7.72.0.0

Indicators of compromise (SHA-256)

ef15c0d417db7dff40efd4fbbed668f2e770a8ac8c16e2c11a54b0102f9ea090

96e63dd12f3157bb49fe3951bfb356c83b4b7349eed5947af87b09c40c868382

9f410ec4f1ed5d9260bd92b9b7dce6e1fc4b639e6752943cb24dba80ffdc0f2b

c1916fb386e86ea60d67da04b36a1ae0d4af64c9383b5b29056cccc3f35d0ac5

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

Campaign

GHSA-753r-q78v-8775IN-MAL-2026-010196IN-MAL-2026-010195IN-MAL-2026-010194

References

Credits

Amazon Inspector · finder

Detect & block this

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